CN109492987A - A kind of synergetic office work method, system and storage medium - Google Patents

Abstract

A kind of synergetic office work method, applied to simultaneously include the first application system and the second application system multi-application system in, the described method includes: if detecting, user account logs on to first application system, and the authentication information of the user account is sent to authentication server and is verified；If being proved to be successful, second application system is automatically logged by the user account.The embodiment of the invention also discloses a kind of cooperative office system and storage mediums.

Description

A collaborative office method, system and storage medium

technical field

The present invention relates to an office system or the field of collaborative office, in particular to a collaborative office method, system and storage medium.

Background technique

With the continuous development of information technology, the relationship between the construction of informatization and the production, operation and management activities of enterprises has become more and more close. The enterprise collaborative office system is a basic information platform built on the basis of IT infrastructure. It covers all users of the enterprise, and users can handle most of the business through one system; they can communicate and coordinate with other members of the work team in real time, and complete tasks efficiently. However, there are still many defects and deficiencies in the existing enterprise collaborative office system. In particular, when faced with a multi-application system, it is necessary to keep in mind a large number of application login information and log in to the multi-application system frequently. Therefore, it is necessary to further improve the enterprise collaborative office system in order to achieve more powerful functions.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a collaborative office method, a collaborative office system, and a storage medium.

In order to achieve the above object, the technical scheme of the present invention is achieved in this way:

A collaborative office method, applied to a multi-application system including a first application system and a second application system at the same time, the method comprising:

If it is detected that the user account is logged into the first application system, the identity verification information of the user account is sent to the verification server for verification;

If the verification is successful, automatically log in to the second application system through the user account.

In the above scheme, the method also includes:

Synchronize user attribute information between the first application system and the second application system; wherein the user attribute information includes: a user account;

The user account is used to log in to the first application system and/or the second application system.

In the above solution, the user attribute information further includes at least one of the following:

Information about the department to which the user belongs, and information about the organization described by the user; the organization includes at least one department.

In the above scheme, the method also includes:

synchronizing the changed job status between the first application system and the second application system;

Wherein, the job status includes but is not limited to at least one of the following:

Job pending status, job pending status, and job processed status.

In the above scheme, the method also includes at least one of the following:

display the content of the portal;

display the content of the page;

display the content of the widget;

Wherein, the portal includes at least one page; the page includes at least one component.

In the above solution, the components include custom components;

Wherein, the custom component includes but is not limited to at least one of the following:

Shortcuts, frequently used links, multi-level tree menus.

In the above scheme, the method also includes at least one of the following:

organizational structure configuration;

User rights configuration;

The organizational structure represents the organization to which the user belongs and/or the department to which the user belongs and/or the basic information of the user.

In the above scheme, the method also includes at least one of the following:

A schedule for creating the first user account;

sharing the schedule of the first user account with the second user account;

Initiate a meeting hosted by the first user;

sharing the meeting of the first user with the second user;

assign a task to the first user;

The task of the first user is shared with the second user.

In the above solution, the assigning a task to the first user includes:

According to the capability requirement of the task and the execution capability parameter of the first user, a task is allocated to the first user whose execution capability meets the capability requirement of the task.

In the above scheme, the method also includes:

Process the job process according to the process node;

The processing job flow includes, but is not limited to, at least one of the following: an application job flow, a viewing job flow, an approval job flow, a monitoring job flow, a privilege intervention job flow, and a statistics job flow.

In the above solution, the operation includes but is not limited to at least one of the following: schedule, meeting, task, request for leave, and business trip.

In the above scheme, the method also includes:

Publish basic corporate information and/or online activity surveys and/or training activity management.

In the above scheme, the method also includes at least one of the following:

Manage document authoring, manage document review, manage document approval, manage document publishing, archiving, manage document delivery, and manage document destruction.

In the above scheme, the method also includes:

Manage the dispatch or destruction or handover of archived documents.

The invention also discloses a collaborative office system, the system includes: a first application system, a second application system and an integrated framework module; wherein,

The integrated framework module is configured to send the identity verification information of the user account to a verification server for verification if it is detected that the user account is logged into the first application system;

If the verification is successful, log the user account into the second application system through the identity verification information.

In the above solution, the integration framework module is further configured to synchronize user attribute information between the first application system and the second application system; wherein the user attribute information includes: a user account;

The user account is used to log in to the first application system and/or the second application system.

In the above solution, the user attribute information further includes at least one of the following:

Information about the department to which the user belongs, and information about the institution to which the user belongs; the institution includes at least one department.

In the above solution, the integrated framework module is further configured to synchronize the changed operation status between the first application system and the second application system;

Wherein, the job status includes but is not limited to at least one of the following:

Job pending status, job pending status, and job processed status.

In the above solution, the system includes: a portal management module; wherein,

The portal management module is used to display job content.

In the above solution, the portal management module includes: a portal management unit, a page management unit, and a component management unit; wherein,

The portal management unit is used to display the content of the portal;

the page management unit, used to display the content of the page;

the component management unit, used to display the content of the component;

Wherein, the portal includes at least one page; the page includes at least one component.

In the above solution, the components include custom components;

Wherein, the custom component includes but is not limited to at least one of the following:

Shortcuts, frequently used links, multi-level tree menus.

In the above solution, the system further includes: a basic configuration management module; wherein,

The basic configuration management module is used for organizational structure configuration and/or user rights configuration;

The organizational structure represents the organization to which the user belongs and/or the department to which the user belongs and/or the basic information of the user.

In the above solution, the system further includes a coordination management module; wherein,

The coordination management module includes: a schedule management unit, a conference management unit, and a task management unit; wherein,

the schedule management unit, configured to create the schedule of the first user account; and/or, share the schedule of the first user account to the second user account;

the conference management unit, configured to initiate a conference hosted by the first user; and/or, share the conference of the first user with the second user;

The task management unit is configured to assign a task to the first user; and/or share the task of the first user to the second user.

In the above solution, the task management unit is further configured to assign a task to the first user whose execution capability meets the task capability requirement according to the capability requirement of the task and the execution capability parameter of the first user.

In the above solution, the system further includes: a process management module; wherein,

The process management module is used to process the job process according to the process node;

The processing job flow includes, but is not limited to, at least one of the following: an application job flow, a viewing job flow, an approval job flow, a monitoring job flow, a privilege intervention job flow, and a statistics job flow.

In the above solution, the operation includes but is not limited to at least one of the following: schedule, meeting, task, request for leave, and business trip.

In the above scheme, the system further includes: a cultural management module; wherein,

The culture management module is used for publishing basic information of the enterprise and/or online activity survey and/or training activity management.

In the above solution, the system further includes: a document management module; wherein,

The document management module is used for at least one of the following: managing document writing, managing document reviewing, managing document approval, managing document publishing, managing document archiving, managing document delivery, and managing document destruction.

In the above scheme, the document management module includes: a file management unit;

The archives management unit is used to manage and manage the delivery or destruction or handover of archives documents.

The present invention also discloses a computer storage medium. The storage medium contains computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the collaborative office method provided by any embodiment of the present invention.

The collaborative office method, collaborative office system, and storage medium provided by the embodiments of the present invention are applied to a multi-application system including a first application system and a second application system. If it is detected that a user account logs in to the first application The system sends the identity verification information of the user account to the verification server for verification; if the verification is successful, automatically log in to the second application system through the user account. In this way, in a multi-application system, by logging in a user account in one application system, the user account can be automatically logged in in other application systems, that is, single sign-on at the user level is realized. In this way, it is not necessary to memorize the login information of a large number of application systems and perform complicated login operations, and realize all application systems that use a set of user passwords to log in to the multi-application systems.

Description of drawings

1 is a schematic flowchart of an embodiment of a collaborative office method according to the present invention;

Fig. 2 is the realization flow schematic diagram of identity authentication in one embodiment;

3 is a schematic flowchart of an embodiment of a collaborative office method according to the present invention;

4 is a schematic flowchart of an embodiment of a collaborative office method according to the present invention;

5 is a schematic flowchart of an embodiment of a collaborative office method according to the present invention;

6 is a schematic structural diagram of a collaborative office system in an embodiment of the present invention;

FIG. 7 is a schematic diagram of a hardware structure of a server of a collaborative office system according to an embodiment of the present invention.

Detailed ways

Collaborative office is mainly applied to the collaborative office of enterprises; of course, the collaborative office can also be based on the collaborative office of the school, the collaborative office of the unit, or the collaborative office of any other organization or institution.

Among them, enterprise collaborative office can help enterprises consolidate management; through integration with other application systems, realize portal function, integrate application system information and data, achieve unified management, expand business activity management to key business links, and enhance business value; Effective strategic control is realized through strategic performance, plan management and data management; through personalized portal integration, personalized content and functional organization configuration can be realized, and composite applications can be formed to meet the needs of different groups of people.

However, the existing methods for realizing enterprise collaborative office still have the following problems:

(1) There is no unified entrance with other application systems, and the single sign-on of users cannot be realized;

With the development of enterprise business, there are more and more information systems in the enterprise, which causes users to repeatedly input user names and passwords, and log in to the system with complicated steps. At the same time, users need to keep in mind the login information of a large number of application systems, otherwise they cannot log in. Because the existing enterprise collaborative office system does not form a unified entry for the application system, it is impossible to log in to all application systems with a set of user names and passwords, and it is impossible to log in to one application system through a user in multiple application systems. User login to other application system trust.

(2) Failure to achieve organizational structure synchronization;

The existing collaborative office method of enterprises does not form a mechanism that other application systems can retrieve and synchronize the organizational structure from the collaborative office system in real time or at regular intervals. Therefore, the existing collaborative office method of enterprises does not realize the unification of the organizational structure of the enterprise information system. management and maintenance functions. Therefore, other application systems need to maintain their own set of organizational structures. In this way, the source of user data is not unified, and the administrator has a lot of operation and maintenance work.

(3) There is no unified to-do;

The existing collaborative office method of enterprises is not deeply integrated with other application systems, forming the function of uniformly pushing to-do tasks of each application system to the portal system and displaying them, resulting in that users need to log in to each application system before to-do work. In this way, the user needs to switch frequently among the various systems, the work is cumbersome, and the real-time performance is poor.

(4) The maintenance of the system portal interface is cumbersome and the user experience is poor;

The portal interface of the existing enterprise collaborative office system requires front-end programmers to implement a large number of development codes, and needs to manually ensure its style consistency and compatibility during the development process, which greatly reduces the development efficiency. Moreover, the maintenance of the portal and the update of the content often require professionals to maintain, which greatly increases the maintenance cost. In this way, the existing enterprise collaborative office results in the constant portal interface, the untimely update of the portal content, and the poor user experience.

(5) The fine-grained user rights are poor, the three-member management mechanism is lacking, and the system security and reliability are lacking;

In the existing collaborative office method of enterprises, the division of user permissions is not fine-grained enough, and the scope of use and permissions are not comprehensively considered according to roles, positions, departments, and business scopes. Moreover, it does not realize the management mechanism of separation of powers, that is, the responsibilities of system administrators, security administrators, and audit administrators are relatively clear and mutually restrictive. In this way, the existing enterprise collaborative office has a security risk that the administrator authority is too large.

Based on the problems existing in the known enterprise collaborative office methods, the embodiments of the present invention provide a method, a system and a storage medium for enterprise collaboration, which can at least solve some of the above-mentioned problems. The implementation, functional characteristics and advantages of the present invention will be further described with reference to the accompanying drawings in conjunction with the embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

The collaborative office method provided by the embodiment of the present invention can be applied to a server, and the functions to be implemented by the method can be implemented by calling a program code by a processor in a terminal. Of course, the program code can be stored in a computer storage medium. It can be seen that the server At least a processor and a storage medium are included.

As shown in FIG. 1 , an embodiment of the present invention provides a collaborative office method, which is applied to a multi-application system including a first application system and a second application system. The method includes:

Step 101: If it is detected that a user account is logged into the first application system, the identity verification information of the user account is sent to a verification server for verification.

Here, in some embodiments, the identity verification information is the login name and password of the user account; in other implementation examples, the identity verification information is the unique identifier of the user account.

Here, the first application system is any application system in the multi-application system; the first application system may be various application software systems.

Here, the second application system is another application system in the multi-application system; the second application system may be various application software systems.

In some embodiments, the first application system is any application system in the multi-application system, and the second application system is all other application systems in the multi-application system except the first application system .

Here, the authentication server may be a PC, or other electronic devices.

Step 103, if the verification is successful, automatically log in to the second application system through the user account.

Specifically, if it is determined at the verification server side that the authentication of the identity verification information is passed, the user can log in automatically in the second application system according to the user account.

In one embodiment, as shown in FIG. 2 , an implementation manner of identity authentication is disclosed, and the method for identity authentication mainly includes the following steps:

Step S01, the terminal server sends the first access request of the user account to the application system server;

Step S02, the application system server determines whether there is an identity ticket of the user account; if not, redirects the first access request to a login verification server;

Wherein, the identity ticket is the information stored in the local database to identify the user account.

Step S03, the login verification server inquires whether the user account is logged in; if not, sends a login request to the terminal server;

Step S04, the terminal server receives the login request; sends a response to the login request to the login verification server according to the login request; wherein the response carries identity information;

Here, the identity information is information used for logging in by the user account.

In one embodiment, the identity information is the password of the user account.

Step S05, the login verification server verifies the identity information of the user; if the identity information verification is passed, an identity ticket of the user account is generated; the identity ticket is sent to the application system server;

Step S06, the application system server generates a verification request according to the identity ticket; sends the verification request to the login verification server;

Step S07, the login verification server receives the verification request; determines whether the identity ticket is valid; if valid, the identity ticket verification passes; if it is determined that the identity ticket verification passes, the user account is sent to the application system server; and , delete the identity ticket;

Step S08, the application system server verifies the identity information of the user account; if the identity information verification is passed, the user account is successfully logged in;

Step S09, if the user account is successfully logged in, the application system server returns the access resource to the terminal server.

In this embodiment, single sign-on at the user level can be implemented, that is, in a multi-application system, automatic login in other application systems can be realized by logging in in one application system; Login information and perform complicated login operations, and realize all application systems that use a set of user passwords to log in to the multi-application system.

As shown in Figure 3, the method further includes:

Step 105: Synchronize user attribute information between the first application system and the second application system; wherein the user attribute information includes: a user account; the user account is used to log in to the first application system and/or Second application system.

In one embodiment, the attribute information may be synchronized between the first application system and the second application system at predetermined time intervals.

In another embodiment, if it is detected that the user attribute information of the first application system changes, the user attribute information of the first application system is synchronized to the second application system.

Here, when the user attribute information of the first application system changes, the changed user attribute information may also be synchronized to the second application system.

Further, the user attribute information also includes at least one of the following:

Information about the department to which the user belongs, and information about the institution to which the user belongs; the institution includes at least one department.

Optionally, the user attribute information further includes: user's post information.

In this embodiment, the user attribute information in one application system can be synchronized to other logged in application systems, that is, the user account of one application system in the multi-application system, the department to which the user belongs, the institution to which the user belongs, or The position information to which the user belongs is synchronized to other application systems, thereby realizing the synchronization of the organizational structure; thus, the internal multi-application systems of the enterprise have a set of the same organizational structure, so that the user data sources are consistent. In this way, the collaborative work between enterprises can be completed more efficiently, and the workload of operation and maintenance can be reduced.

As shown in Figure 4, the method further includes:

Step 107, synchronizing the changed job status between the first application system and the second application system;

Wherein, the job status includes but is not limited to at least one of the following:

Job pending status, job pending status, and job processed status.

Here, the job agent state is a state in which a job needs to be processed but has not been processed; the job pending state is a state in which a job needs to be viewed; and a job processed state is a state in which the job has been completed.

Optionally, when the job status of the user account of the second application system changes, the job status of the changed user account of the second application system is synchronized to the first application system.

In this embodiment, the integrated management of jobs can be realized, so that after logging in one of the application systems, the user can process the jobs that need to be processed by other application systems, thereby reducing the frequent switching of the user among the application systems, thereby reducing the workload, Improved work efficiency.

As shown in Figure 5, the method further includes at least one of the following:

In step 201, the content of the portal is displayed; the content of the page is displayed; the content of the component is displayed; wherein the portal includes at least one page; the page includes at least one component.

Here, the portal may be a portal website such as Sina, NetEase, Sohu, Tencent, Baidu Xinhuanet, etc.

Here, the portal may also be an enterprise-level portal, a department-level portal, a special portal, a project collaboration portal, or a personal portal.

Here, the portal is a carrier of pages, and a portal may include multiple pages.

Optionally, the server may configure the content of the portal and/or pages and/or components by means of creating and/or copying and pasting.

Further, the components include: custom components;

Wherein, the custom component includes but is not limited to at least one of the following:

Shortcuts, frequently used links, multi-level tree menus.

Specifically, components can be defined by customizing shortcuts, common connections, multi-level tree menus, etc. by creating them.

Here, the components further include: system components;

Wherein, the system component is a component provided by the local memory.

In one embodiment, the configuration method of the portal is as follows:

Step S11: planning the overall structure of the portal;

Specifically, plan the type of portal, and the pages the portal contains. For example, the type of the planned portal is an enterprise portal, or a project collaboration portal, or a personal portal; for another example, the planned portal includes 10 pages, or includes 25 pages.

Step S12: planning the layout of the page;

Specifically, plan the number of rows and columns of the page, and the components that the page contains.

Step S13: create a custom component;

Specifically, custom widgets that are created for the configuration of the page. For example, you can create custom widgets for multi-level tree menus and configure URL addresses for quick access. Of course, you can also call system components for page configuration.

Step S14: create a page;

Specifically, pages can be divided into multiple containers; system components and/or custom components are added to the containers.

Wherein, the container is a window divided according to the entire page, and one container represents one window; the component can be added to the container.

Step S15: Create a portal.

Specifically, a portal may be configured through one or more configured pages; wherein, the configured one or more pages may refer to a page that existed before, or a currently configured page.

In this embodiment, the content in the portal can be configured according to the user's needs; specifically, the content of the page can be configured according to the user-defined components and/or system components; the content of the portal can be configured according to the content of the page.

In this embodiment, the configuration of multi-level, project collaboration portals and other special portals such as enterprise portals, department portals, and personal portals, as well as multi-functional portals, etc. can also be realized; thus, flexible and automatic multi-level and multi-functional portals can be realized. Configuration, so that different user accounts can be assigned to process related jobs in the content of the portal according to the application scope and requirements of different portals. In this way, the cost of human resources can be saved, and the user experience can be improved.

As shown in Figure 5, the method further includes at least one of the following:

Step 203, organization structure configuration; user rights configuration; wherein, the organization structure represents the basic information of the user's organization and/or the department to which the user belongs and/or the user.

Here, the organizational structure configuration may be the establishment and maintenance of user information; the user information may be the user's serial number, and/or the login name of the user account, and/or the security level of the user account, and/or the user's Post information, and/or the serial number of the department to which the user belongs, and/or the serial number of the institution mentioned by the user, etc.; wherein, the post information also includes: the serial number to which the post belongs, and the detailed description of the post.

Here, the organizational structure configuration may include organization management, department management, or personnel management.

Here, the permission configuration includes being responsible for setting and maintaining user permissions.

In some embodiments, the authority set for the organizational structure configuration is the system administrator account to have the use authority, and other user accounts have no use authority; the authority set for the authority configuration is the security administrator account to have the use authority, and other users have the right to use. The account does not have permission to use it.

In other embodiments, the authority set for the system configuration is the system administrator account to have the use authority, and the accounts of other users have no use authority; the authority set for the management and operation of the log is the audit administrator account to have the use authority Permissions, other user's accounts do not have permission to use.

Here, the method may further include: system configuration; and/or operation and maintenance monitoring configuration.

Here, the method may also include some other configurations.

In this embodiment, through the configuration of the organizational structure, a clear user account structure can be established, so that the user's department, organization or personal information can be quickly searched; the functions and permissions of each user account can be quickly obtained.

In this embodiment, the specific rights of the user can be known by configuring the rights of the user; further, if the rights for managing different functions are respectively assigned to different user accounts, a mechanism for managing different functions based on different administrators can be implemented, avoiding the need for Only adopting the one-member management mechanism leads to the problem that the authority of the one-manager is too large. For example, a three-member management mechanism of a system administrator, a security administrator, and an audit administrator can be adopted, so that the administrators of the three members restrict each other and jointly complete the operation and maintenance of the system. In this way, the permissions assigned by the users are divided in detail, which solves the problem of insufficient fine-grained user permissions.

As shown in Figure 5, the method further includes at least one of the following:

Step 205, creating a schedule of the first user account; sharing the schedule of the first user account with the second user;

Initiating a conference hosted by the first user; sharing the conference of the first user with the second user;

Assign a task to the first user; share the task of the first user with the second user.

Here, the schedule may include schedules of meetings, tasks, business trips, and requests for leave.

Here, creating a schedule may be creating a personal schedule, or creating a schedule for multiple people; the creating schedule may also be creating a department's schedule.

In some implementations, both the first user and the second user may be characterized as one user or multiple users.

In other embodiments, both the first user and the second user may be characterized as one department or multiple departments.

Here, the multiple refers to two or more.

Here, the creation schedule may be the time, place, and person at which the schedule is created.

Here, the creation of the schedule may also be a reminder strategy, reminder method, reminder purpose, and the like for the creation of the schedule.

Here, one way of creating a schedule is to automatically generate a corresponding schedule according to the data provided by the application.

Optionally, the server creates a schedule of the first user account; after the schedule is created, shares the schedule of the first user with the second user.

Here, the time, place, participants, agenda content, meeting materials, meeting approval, etc. of the meeting held can be sent to the participants in the form of electronic cards.

Here, the meeting document can be reminded by the server; wherein, the meeting document includes the meeting arrangement time, location, person, etc.; when the prepared meeting document is submitted, if approved, the meeting document will be automatically released; The above conference documents are authorized to the relevant user account to view.

In one embodiment, before initiating a conference hosted by the first user, statistics are made on the throughput of the conference and the utilization rate of the conference room; participants are reasonably arranged according to the conference throughput; and the utilization rate of the conference room is reasonable Schedule a meeting time.

Here, the task may be a business that needs to be executed.

Here, the task can be decomposed into multiple subtasks.

Here, the task includes but is not limited to the following elements: task name, task recipient, task completion time, and task content description.

Here, one way of assigning a task to the first user is to assign a task to the first user according to the elements of the task.

Optionally, after it is received that the first user has performed the assigned task, evaluation and/or feedback and/or analysis of the execution situation may be performed.

Further, the assigning a task to the first user includes:

According to the capability requirement of the task and the execution capability parameter of the first user, a task is allocated to the first user whose execution capability meets the capability requirement of the task.

The execution capability parameter of the first user is the load degree of the task received by the first user and/or the satisfaction evaluation value of the execution task.

In this embodiment, by creating a schedule, the user's work can be reminded in real time; by publishing a conference, an instant reminder can be realized for participants in the conference to see the conference; and tasks can be assigned to the user reasonably. In this way, faster and more efficient collaborative work can be achieved between departments or between employees.

As shown in Figure 5, the method further includes:

Step 207: Process the job flow according to the flow node; wherein, the processing job flow includes but is not limited to at least one of the following: application job flow, viewing job flow, approval job flow, monitoring job flow, privileged intervention job flow, and statistics job flow .

Further, the homework includes but is not limited to at least one of the following: schedule, meeting, task, request for leave, and business trip.

Here, the application work flow may be started by filling in the relevant content according to the template, and then starting the application work flow.

Here, for viewing the job flow, the node where the job flow is located may be viewed.

Here, in the approval work flow, approval processes such as rejection, rejection, transfer, communication, and signature can be performed on the job.

Here, the monitoring job process can monitor the node where the job is located in real time, and feed it back to the corresponding executor; specifically, it can be represented by a graphical process trend.

Here, the privilege intervenes in the job flow, and may perform intervention processing on some abnormal flow nodes; for example, for a job flow that has been stuck in a certain flow node for a long time, the job flow is directly transferred to the next flow node; or, For the process node when an error occurs in the processing process, you can return to the previous process node for processing.

Here, the statistical work flow can be counted according to the category of the title, the state of the document, the number of user applications, and the like.

Here, the operation process may be an operation process of human resources, comprehensive management, material procurement, asset management, project management, and the like.

In one embodiment, a method for making a process template is disclosed. The method for making a process template includes the following steps:

Step S21, define the template name; determine the attributes of the template;

Here, the categories of the templates include: human resources, comprehensive management, material procurement, asset management, project management, and the like.

Specifically, the name of the template is defined; the attributes of the template are determined according to the category of the template.

Step S22, making a flow sheet of the template;

Specifically, the time, date, serial number, applicant, and subject options of the template are created to define the process form of the template.

Step S23, making an approval form;

Specifically, the layout position of the plug-in, the attributes of the plug-in, the display content of the plug-in, and the appearance size of the plug-in are configured to define the process form of the template.

Here, the plug-in includes but is not limited to at least one of the following: a text box, a radio button, a multi-select button, a drop-down button, an address book, a time box, an attachment box, and an approval operation.

Step S24, making an approval processing flow;

Specifically, a graphical process tool is used to create an approval process direction; wherein, the process direction is: start node, draft node, approval node, decision node, signature node, CC node, end node, etc.; configure corresponding nodes for each node. the handling of users and the manner in which they operate;

Step S25, configure the template authority, and set the user of the template;

Step S26, configure the print properties, and set the print content of the approval form.

In this embodiment, the integration of the operation process can be realized, and the collaborative management centered on the process can be realized, so that the operations are processed between departments and employees according to their own processes. Furthermore, since the job flow can be divided into different job flow categories according to the business, flow management centered on business classification can be implemented.

As shown in Figure 5, the method further includes:

Step 209: Publish basic information of the enterprise and/or online activity survey and/or training activity management.

Here, the basic information of the enterprise may be news of the enterprise, and the news may be link news or multimedia news; the basic information of the enterprise may be the announcement or notification of the enterprise.

Of course, if it is for schools, or other units or organizations, it can also be the basic information of schools, or other units or organizations.

Here, the online activity survey may be an internal-oriented online survey or a polling activity.

Here, the training activity management may be a training plan, a training courseware, or an exam question bank.

In this embodiment, it is possible to learn about the hot events and basic operation status of the enterprise by publishing basic information of the enterprise; through the investigation of network activities, it can help the construction of enterprise culture and create a good working atmosphere; through the management of training activities, it is possible to improve employees' understanding Job skills for each position. In this way, the collaboration ability between employees can be further improved.

As shown in Figure 5, the method further includes at least one of the following:

Step 211, management document writing, management document review, management document approval, management document release, management document archiving, management document transmission, management document destruction.

Here, the document may be a document document, a normative system, an archive document, a work summary, and the like.

Here, the management of documents also includes: building a knowledge base.

Further, the method further includes: managing the delivery or destruction or handover of the archives.

Specifically, it is possible to manage the delivery or destruction or handover of archive documents by triggering the corresponding action flow.

In this embodiment, documents can be managed in a centralized manner, and the sharing and delivery of documents within the enterprise can be realized, so as to facilitate the retrieval and inspection of employees; .

In this embodiment, confidentiality management of each document can be implemented by combining with the authority setting of the document, thereby improving the security of the document. Different permissions can be set for different document types, so as to implement hierarchical and hierarchical permission settings for the documents.

It should be pointed out here that the following description of the collaborative office system item is similar to the description of the above-mentioned collaborative office method, and the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the embodiments of the collaborative office system of the present invention, please refer to the description of the embodiments of the collaborative office method of the present invention.

As shown in FIG. 6 , an embodiment of the present invention further provides a collaborative office system, which is applied to the application layer S2 ; wherein the system includes a first application system 38 , a second application system 39 and an integrated framework module 31 ; Optionally, the system may further include at least one of the following: a portal management module 32 , a basic configuration management module 33 , a coordination management module 34 , a process management module 35 , a culture management module 36 , and a document management module 37 .

An embodiment of the present invention provides a collaborative office system, the system includes: a first application system 38, a second application system 39, and an integrated framework module 31; wherein,

The integration framework module 31 is configured to send the identity verification information of the user account to the verification server for verification if it is detected that the user account is logged into the first application system;

If the verification is successful, log the user account into the second application system through the identity verification information.

Optionally, the integration framework module 31 is further configured to synchronize user attribute information between the first application system and the second application system; wherein the user attribute information includes: a user account;

The user account is used to log in to the first application system and/or the second application system;

Optionally, the user attribute information further includes at least one of the following:

The user's post information, the user's department information, and the user's institution information; the institution includes at least one department.

Here, by developing an organizational structure interface of the Webservice platform for the portal system, other application systems can call the interface for data synchronization.

Here, the synchronized data may be user attribute information; the user attribute information may be the user's department information and the user's institution information; wherein, the institution includes at least one department.

Here, the user attribute information may also specifically be the department number of the user account, the number of the user's post, and so on.

In this embodiment, the user attribute information of one application system, that is, the personnel organization structure of an enterprise, a unit, a school, etc., can be synchronized to another application system in a multi-application system. Moreover, dynamic data synchronization can be realized, and the addition of personnel-corresponding attribute information, the deletion of personnel-corresponding attribute information, and the deletion of personnel-corresponding attribute information in the first application system can be synchronized to the second application system through timing trigger jobs.

Optionally, the integration framework module 31 is further configured to synchronize the changed job status between the first application system and the second application system;

Wherein, the job status includes but is not limited to at least one of the following:

Job pending status, job pending status, and job processed status.

Optionally, the system provides a to-do Webservice platform, and the Webservice platform includes interfaces such as sending to-do (sendTodo), deleting to-do (deleteTodo), setting as done (setTodoDone), and obtaining to-do information (getTodo). . Here, the interface is used for synchronizing the job status of the logged-in user account stored by the first application system to the second application system and transferring data for the job status.

Optionally, the system further includes: a portal management module 32; the portal management module is used for displaying job content.

Optionally, the portal management module includes: a portal management unit 321, a page management unit 322, and a component management unit 323; wherein,

The portal management unit 321 is used to display the content of the portal;

The page management unit 322 is used to display the content of the page;

The component management unit 323 is used to display the content of the component;

Wherein, the portal includes at least one page; the page includes at least one component.

Optionally, the components include custom components;

Wherein, the custom component includes but is not limited to at least one of the following:

Shortcuts, frequently used links, multi-level tree menus.

Optionally, the component includes a system component; the system component is a component provided by a local memory.

Optionally, the components include custom components and/or system components.

Optionally, the system further includes: a basic configuration management module 33; wherein,

The basic configuration management module 33 is used for organizational structure configuration and/or user rights configuration; wherein, the organizational structure represents the organization to which the user belongs and/or the department to which the user belongs and/or the basic information of the user.

Optionally, the basic configuration management module further includes: an organizational structure configuration unit 331 , an authority configuration unit 332 , a system configuration unit 333 , and an operation and maintenance monitoring unit 334 .

Optionally, the system further includes: a coordination management module 34 .

Optionally, the coordination management module 34 further includes: a schedule management unit 341, a conference management unit 342, and a task management unit 343; wherein,

The schedule management unit 341 is configured to create the schedule of the first user account; and/or, share the schedule of the first user account with the second user account;

The conference management unit 342 is configured to initiate a conference hosted by the first user; and/or, share the conference of the first user with the second user;

The task management unit 343 is configured to assign a task to the first user; and/or share the task of the first user to the second user.

Here, the schedule management unit 341 may be used to set a reminder strategy, a reminder method, and a reminder purpose according to the schedule.

Here, the conference management unit 342 can be used for conference arrangement, conference minutes, and conference statistics.

Here, the task management unit 343 can be used for task arrangement, task decomposition, execution feedback, task evaluation, task log generation, and task analysis.

Optionally, the task management unit 343 is further configured to allocate a task to the first user whose execution capability meets the task capability requirement according to the capability requirement of the task and the execution capability parameter of the first user.

Optionally, the system further includes: a process management module 35, wherein:

The process management module 35 is used to process the job process according to the process node;

The processing job flow includes, but is not limited to, at least one of the following: an application job flow, a viewing job flow, an approval job flow, a monitoring job flow, a privilege intervention job flow, and a statistics job flow.

Here, the homework includes, but is not limited to, at least one of the following: schedule, meeting, task, request for leave, and business trip.

Optionally, the process management module 35 includes: a human resources unit 351 , a comprehensive management unit 352 , a material procurement unit 353 , an asset management unit 354 , and a project management unit 355 .

In other embodiments, the process management module 35 includes: an application process unit, an approval process unit, and a monitoring process unit.

Optionally, the system includes: a culture management module 36; wherein,

The culture management module 36 is used for publishing basic information of the enterprise and/or online activity survey and/or training activity management.

Optionally, the culture management module 36 includes: a news management unit 361 , an online investigation unit 362 , and a training management unit 363 .

Here, the news management unit 361 can be used to publish corporate news, announcements, and notices.

Here, the web survey unit 362 may be used for online survey and polling campaign initiation.

Here, the training management unit 363 can be used for the management of training plans, training courseware, and examination question banks.

Optionally, the system further includes: a document management module 37; wherein,

The document management module 37 is used for at least one of the following: managing document writing, managing document reviewing, managing document approval, managing document publishing, managing document archiving, managing document delivery, and managing document destruction.

Optionally, the document management module 37 includes: a document management unit 371, a normative system unit 372, a knowledge center unit 373, a file management unit 374, and a work summary unit 375; wherein,

The archive management unit 374 is used to manage the sending or destruction or handover of archive documents.

The enterprise collaborative office system realizes faster and more efficient collaborative work between departments and employees on a unified information system platform; provides a smooth communication mechanism between employees and adapts to the continuous change and optimization of the process.

The enterprise collaborative office system realizes the functions of unified to-do with other application systems, user's single sign-on, and organizational structure synchronization, integrates enterprise information and data and displays them uniformly; realizes the system and document management with standards and specifications as the core; Collaborative management centered on process and process management centered on business classification; realizes flexible self-service configuration, establishment and maintenance of multi-level and multi-type portals; creates flexible, stable, safe and efficient integrated enterprise information base platform.

Please refer to FIG. 6 again, the system may further include a presentation layer S1, a middleware layer S3, a data layer S4, an operating system layer S5, and an IT infrastructure layer S6; wherein,

The presentation layer S1 is used to provide presentation content for interaction between the system and the user.

The middleware layer S3 is used to provide various components at the bottom of the system.

The data layer S4 is responsible for storing unstructured data and/or structured data.

The operating system layer S5 is used to provide the operating system of the server. For example, a Windows system, a UNIX system, or a Linux system can be provided.

The IT infrastructure layer S6 is used to provide hardware devices for the system. For example, a server, network, storage, etc. may be provided.

An embodiment of the present invention also provides a collaborative office system, which is applied to a server; please refer to FIG. 7 , the server includes a processor 41 and a memory 42 for storing a computer program that can be executed on the processor; wherein , the processor is configured to implement the distributed programming method provided by any embodiment of the present invention when running a computer program.

In some embodiments, memory 42 in embodiments of the present invention may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Wherein, the non-volatile memory may be Read-Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (Erasable PROM, EPROM), Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double DataRate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) and Direct memory bus random access memory (Direct Rambus RAM, DRRAM). The memory 42 of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

The processor 41 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in the processor 41 or an instruction in the form of software. The above-mentioned processor 41 may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other possible Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps, and logical block diagrams disclosed in the embodiments of the present invention can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present invention may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory 42, and the processor 41 reads the information in the memory 42, and completes the steps of the above method in combination with its hardware.

In some embodiments, the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASIC), Digital Signal Processing (DSP), Digital Signal Processing Device (DSP Device, DSPD), programmable logic Devices (ProgrammableLogic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application or a combination thereof.

For a software implementation, the techniques described herein may be implemented through modules (eg, procedures, functions, etc.) that perform the functions described herein. Software codes may be stored in memory and executed by a processor. The memory can be implemented in the processor or external to the processor.

Yet another embodiment of the present invention also provides a computer storage medium, the computer-readable storage medium stores an executable program, and when the executable program is executed by the processor 41, the following steps of the collaborative office method can be implemented:

If it is detected that the user account is logged into the first application system, the identity verification information of the user account is sent to the verification server for verification;

If the verification is successful, automatically log in to the second application system through the user account.

Optionally, when the executable program is executed by the processor 41, it is also used to implement the following steps:

Synchronize user attribute information between the first application system and the second application system; wherein the user attribute information includes: a user account;

The user account is used to log in to the first application system and/or the second application system.

Optionally, when the executable program is executed by the processor 41, it is also used to implement the following steps:

synchronizing the changed job status between the first application system and the second application system;

Wherein, the job status includes but is not limited to at least one of the following:

Job pending status, job pending status, and job processed status.

Optionally, when the executable program is executed by the processor 41, it is also used to implement at least one of the following:

Display the content of the portal; display the content of the page; display the content of the component;

Wherein, the portal includes at least one page; the page includes at least one component.

Optionally, when the executable program is executed by the processor 41, it is also used to implement the following steps:

Organizational structure configuration; and/or, user rights configuration;

The organizational structure represents the organization to which the user belongs and/or the department to which the user belongs and/or the basic information of the user.

Optionally, when the executable program is executed by the processor 41, it is also used to implement at least one of the following:

A schedule for creating the first user account;

sharing the schedule of the first user account with the second user account;

Initiate a meeting hosted by the first user;

sharing the meeting of the first user with the second user;

assign a task to the first user;

The task of the first user is shared with the second user.

Optionally, when the executable program is executed by the processor 41, it is also used to implement the following steps:

According to the capability requirement of the task and the execution capability parameter of the first user, a task is allocated to the first user whose execution capability meets the capability requirement of the task.

Optionally, when the executable program is executed by the processor 41, it is also used to implement the following steps:

Process the job process according to the process node;

The processing job flow includes, but is not limited to, at least one of the following: an application job flow, a viewing job flow, an approval job flow, a monitoring job flow, a privilege intervention job flow, and a statistics job flow.

Optionally, when the executable program is executed by the processor 41, it is also used to implement the following steps:

Publish basic corporate information and/or online activity surveys and/or training activity management.

Optionally, when the executable program is executed by the processor 41, it is also used to implement at least one of the following:

Manage document authoring, manage document review, manage document approval, manage document publishing, archiving, manage document delivery, and manage document destruction.

Optionally, when the executable program is executed by the processor 41, it is also used to implement the following steps:

Manage the dispatch or destruction or handover of archived documents.

In some embodiments, the computer storage medium may include: a USB flash drive, a removable hard disk, a read only memory (ROM, Read Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, etc. A medium on which program code can be stored.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. should be included within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (20)

1. A cooperative working method, applied to a multi-application system including a first application system and a second application system, the method comprising:

if the fact that a user account logs in the first application system is detected, identity authentication information of the user account is sent to an authentication server for authentication;

and if the verification is successful, automatically logging in the second application system through the user account.

2. The method of claim 1, further comprising:

synchronizing user attribute information between the first application system and the second application system; wherein the user attribute information includes: a user account;

the user account is used for logging in the first application system and/or the second application system.

3. The method of claim 2, wherein the user attribute information further comprises at least one of:

information of a department to which the user belongs and information of a mechanism to which the user belongs; the mechanism includes at least one door.

4. The method of claim 1, further comprising:

synchronizing a changed job state between the first application system and the second application system;

wherein the job status includes, but is not limited to, at least one of:

job pending status, and job processed status.

5. The method of claim 1, further comprising at least one of:

presenting the content of the portal;

displaying the content of the page;

presenting the content of the part;

wherein the portal comprises at least one page; the page includes at least one part.

6. The method of claim 5,

the parts comprise custom parts;

wherein the custom part includes, but is not limited to, at least one of:

shortcuts, common links, multi-level tree menus.

7. The method of claim 1, further comprising at least one of:

organizing the architectural configuration;

configuring user authority;

wherein, the organization architecture represents the basic information of the organization and/or the department and/or the user to which the user belongs.

8. The method of claim 1, further comprising at least one of:

creating a schedule of a first user account;

sharing the schedule of the first user account to a second user account;

initiating a conference hosted by a first user;

sharing the conference of the first user to a second user;

assigning a task to a first user;

and sharing the task of the first user to a second user.

9. The method of claim 8,

the assigning the task to the first user comprises:

and distributing the task to the first user with the execution capacity meeting the task capacity requirement according to the capacity requirement of the task and the execution capacity parameter of the first user.

10. The method of claim 1, further comprising:

processing the operation flow according to the flow node;

wherein the processing workflow includes, but is not limited to, at least one of: applying for the operation flow, checking the operation flow, examining and approving the operation flow, monitoring the operation flow, interfering the operation flow with privilege and counting the operation flow.

11. The method of claim 10,

the job includes, but is not limited to, at least one of: schedule, meeting, task, leave, business trip.

12. The method of claim 1, further comprising:

and issuing enterprise basic information and/or online activity investigation and/or training activity management.

13. The method of claim 1, further comprising at least one of:

managing the writing of documents, managing the review of documents, managing the approval of documents, managing the publishing of documents, managing the archiving of documents, managing the delivery of documents, managing the destruction of documents.

14. The method of claim 1, further comprising:

managing the export or destruction or handover of archive documents.

15. A collaborative office system, the system comprising: a first application system, a second application system and an integrated framework module; wherein,

the integrated framework module is used for sending the identity authentication information of a user account to an authentication server for authentication if the fact that the user account logs in the first application system is detected;

and if the verification is successful, logging the user account in the second application system through the identity verification information.

16. The system of claim 15, wherein the system comprises: a portal management module; wherein,

and the portal management module is used for presenting the operation content.

17. The system of claim 16, wherein the portal management module comprises: a portal management unit, a page management unit and a component management unit; wherein,

the portal management unit is used for showing the content of the portal;

the page management unit is used for showing the content of the page;

the component management unit is used for showing the content of the component;

wherein the portal comprises at least one page; the page includes at least one part.

18. The method of claim 15, wherein the system further comprises: a basic configuration management module;

the basic configuration management module is used for organizing architecture configuration and/or user permission configuration;

wherein, the organization architecture represents the basic information of the organization and/or the department and/or the user to which the user belongs.

19. The system of claim 15, further comprising: a process management module; wherein,

the flow management module is used for processing the operation flow according to the flow node;

wherein the processing workflow includes, but is not limited to, at least one of: applying for the operation flow, checking the operation flow, examining and approving the operation flow, monitoring the operation flow, interfering the operation flow with privilege and counting the operation flow.

20. A storage medium having computer-executable instructions stored therein, the computer-executable instructions being executable by a processor to perform a method of performing the collaborative office of any of claims 1-14.