KR102406854B1 - Work managing apparatus related file and the method thereof - Google Patents

Abstract

a memory and a processor electrically connected to the memory, wherein the processor is associated with a file in a folder shared by one or more folder sharers and creates a file chat room accessed through the file, the user terminal of the one or more folder sharers A message thread including a log message corresponding to the update history is received from the user terminal according to the update of the file by There is provided a file-associated work management apparatus, characterized in that a conversation message between folder sharers and the log message are displayed together.

Description

File-linked work management device {WORK MANAGING APPARATUS RELATED FILE AND THE METHOD THEREOF}

The present invention relates to a work management technology, and more particularly, to a technology for recording changes and corrections of files together with conversation contents while performing a task through a chat room for each file.

In general, an Internet messenger corresponds to an application that transmits a message including text or graphics between users, and may be implemented as a chat room in which a plurality of users participate. In an embodiment, the Internet messenger may include a mobile messenger performed in a mobile environment (eg, a mobile phone), and may include, for example, KakaoTalk, Line, WeChat, Facebook Messenger, and the like. In addition, these Internet messengers are increasingly being used in various ways in business management and processing.

Patent Publication No. 10-2004-0100425 (2004.12.02)

According to an embodiment of the present invention, for a file related to work, it is an object to provide a communication tool between work members through a chat room linked to the file. In addition, according to an embodiment of the present invention, when a modification or change by members occurs for a specific file, it is possible to record the modification details through the chat room associated with the file together with the file itself, and a work processing technology associated with the chat room. would like to provide

Among embodiments, a memory and a processor electrically coupled to the memory, wherein the processor creates a file chat room associated with and accessed through a file object in a folder shared by one or more folder sharers, one A message thread including a log message corresponding to the update details received from the user terminal according to the update of the file object by the user terminal of the folder sharer is displayed in the file chat room, wherein the file chat room There is provided a file-associated task management apparatus, characterized in that the log message and the conversation message between one or more folder sharers related to the file object are displayed together.

In addition, in the task management method performed by the file-associated task management device including a memory and a processor electrically connected to the memory, it is associated with a file object in a folder shared by one or more folder sharers, and through the file object creating an accessible file chat room; receiving, from the user terminal, update details according to the update of the file object by the user terminal of one or more of the folder sharers; and displaying a message thread including a log message corresponding to the update history in the file chat room, wherein the file chat room includes a chat message between one or more folder sharers related to the file object and the log message together There is provided a file-linked business management method, characterized in that it is displayed.

In addition, in a recording medium recording a computer program related to a computer-executable file-linked business management method, (a) a file chat room related to a file object in a folder shared by one or more folder sharers and accessible through the file object; the ability to create; (b) a function of receiving an update history according to an update of the file object by a user terminal of one or more of the folder sharers; and (c) displaying a message thread including a log message corresponding to the update details in the file chat room, wherein the file chat room includes a chat message between one or more folder sharers related to the file object and the log There is provided a recording medium recording a computer program for a computer-executable file-linked business management method, characterized in that the message is displayed together.

The disclosed technology may have the following effects. However, it does not mean that a specific embodiment should include all of the following effects or only the following effects, so the scope of the disclosed technology should not be understood as being limited thereby.

According to an embodiment of the present invention, for a file related to work, a communication tool between work members may be provided through a chat room linked to the file. In addition, according to an embodiment of the present invention, when a modification or change by members occurs with respect to a specific file, it is possible to record the revision history through the chat room associated with the file together with the file itself, and a work processing technology associated with the chat room. can provide

1 is a view showing a file-linked business management system according to an embodiment of the present invention.
Figure 2 is a block diagram of a file-associated task management apparatus according to an embodiment of the present invention.
Figure 3 is a block diagram of a processor in the file-associated task management apparatus according to an embodiment of the present invention.
4 is a flowchart illustrating a file-associated task management method according to an embodiment of the present invention.
5 is a flowchart illustrating a file-associated task management method according to another embodiment of the present invention.
6 is a flowchart illustrating a file-associated task management method according to another embodiment of the present invention.

Since the description of the present invention is merely an embodiment for structural or functional description, the scope of the present invention should not be construed as being limited by the embodiment described in the text. That is, since the embodiment may have various changes and may have various forms, it should be understood that the scope of the present invention includes equivalents capable of realizing the technical idea. In addition, since the object or effect presented in the present invention does not mean that a specific embodiment should include all of them or only such effects, it should not be understood that the scope of the present invention is limited thereby.

On the other hand, the meaning of the terms described in the present application should be understood as follows.

Terms such as “first” and “second” are for distinguishing one component from another, and the scope of rights should not be limited by these terms. For example, a first component may be termed a second component, and similarly, a second component may also be termed a first component.

When a component is referred to as being “connected to” another component, it may be directly connected to the other component, but it should be understood that other components may exist in between. On the other hand, when it is mentioned that a certain element is "directly connected" to another element, it should be understood that the other element does not exist in the middle. Meanwhile, other expressions describing the relationship between elements, that is, "between" and "between" or "neighboring to" and "directly adjacent to", etc., should be interpreted similarly.

The singular expression is to be understood as including the plural expression unless the context clearly dictates otherwise, and terms such as "comprises" or "have" refer to the embodied feature, number, step, action, component, part or these It is intended to indicate that a combination exists, and it should be understood that it does not preclude the possibility of the existence or addition of one or more other features or numbers, steps, operations, components, parts, or combinations thereof.

In each step, identification numbers (eg, a, b, c, etc.) are used for convenience of description, and identification numbers do not describe the order of each step, and each step clearly indicates a specific order in context. Unless otherwise specified, it may occur in a different order from the specified order. That is, each step may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order.

The present invention can be embodied as computer-readable codes on a computer-readable recording medium, and the computer-readable recording medium includes all types of recording devices in which data readable by a computer system is stored. . Examples of the computer-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like. In addition, the computer-readable recording medium is distributed in a computer system connected to a network, so that the computer-readable code can be stored and executed in a distributed manner.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs, unless otherwise defined. Terms defined in general used in the dictionary should be interpreted as having the meaning consistent with the context of the related art, and cannot be interpreted as having an ideal or excessively formal meaning unless explicitly defined in the present application.

1 is a diagram illustrating a file-associated work management system 100 according to an embodiment of the present invention.

Referring to FIG. 1 , the file-associated task management system 100 includes a file-associated task management device 110 and one or more user terminals 120 .

The file-associated task management device 110 corresponds to a computing device that can be connected to at least one user terminal 120 through a network. In an embodiment, the file-associated task management apparatus 110 may manage at least one member group in which a user associated with the user terminal 120 is included as a member.

In one embodiment, the file-associated task management device 110 may be connected to the user terminal 120 through a shared folder agent installed in the user terminal 120 , where the shared folder agent is connected to the user terminal 120 . When installed, it corresponds to an agent program, which is software that allows the user terminal 120 and the file-associated task management device 110 to interwork with each other under the approval of the user terminal 120 .

The user terminal 120 corresponds to a computing device that can be connected to the folder management device 110 through a network, and may be, for example, a user terminal implemented as a desktop, notebook, tablet PC, or smart phone.

In an embodiment, the first user terminal 120a may be a mobile terminal, and may be connected to the file-associated task management apparatus 110 through cellular communication or Wi-Fi communication. In another embodiment, the second user terminal 120b may be a desktop, and may be connected to the file-associated task management apparatus 110 through the Internet. And here, the first user and the second user corresponding to the first user terminal 120a and the second user terminal 120b are folder sharing participants who jointly participate in the shared folder, or a file having access to the shared file. They may be shared participants.

2 is a block diagram of the file-associated task management apparatus 110 according to an embodiment of the present invention.

Referring to FIG. 2 , the file-associated task management apparatus 110 may include a processor 210 , a memory 220 , a user input/output unit 230 , and a network input/output unit 240 .

The processor 210 may execute a file-associated business management procedure according to an embodiment of the present invention, and may manage the memory 220 read or written in this process, and the volatile memory in the memory 220 and Synchronization time between non-volatile memories can be scheduled.

The processor 210 may control the overall operation of the file-associated task management device 110 , and is electrically connected to the memory 220 , the user input/output unit 230 , and the network input/output unit 240 to flow data therebetween. can be controlled. The processor 210 may be implemented as a central processing unit (CPU) of the file-associated task management device 110 . A more detailed operation of the processor 210 will be described in detail later with reference to FIG. 3 .

The memory 220 is implemented as a non-volatile memory such as a solid state disk (SSD) or a hard disk drive (HDD) and includes an auxiliary storage device used to store overall data required for the file-associated work management device 110 . and may include a main memory implemented as a volatile memory such as random access memory (RAM). As such, the memory 220 may be implemented as a volatile and non-volatile memory, and if implemented as a non-volatile memory, may be implemented to be connected through a hyperlink.

The user input/output unit 230 includes an environment for receiving a user input and an environment for outputting specific information to the user, for example, a mouse, a trackball, a touch pad, a graphic tablet, a scanner, a touch screen, a keyboard, or a pointing device. It may include an input device including an adapter, such as a device, and an output device, including an adapter, such as a monitor or touch screen. In an embodiment, the user input/output unit 230 may correspond to a computing device accessed through remote access, and in such a case, the file-associated task management device 110 may serve as a server.

The network input/output unit 240 includes an environment for connecting to the user terminal 120 through a network, and may include, for example, an adapter for LAN (Local Area Network) communication.

3 is a block diagram of the processor 210 in the file-associated task management apparatus 110 according to an embodiment of the present invention.

According to the embodiment described with reference to FIG. 3 , the processor 210 controls the file system manager 310 , the chat room generator 320 , the controller 330 , the log message manager 340 , and the chat message manager 350 . may include However, the processor 210 according to an embodiment of the present invention does not have to include all of the above components at the same time, and according to each embodiment, some of the above components may be omitted, and some of the above components may be omitted. Or it may optionally include all of them.

The file system management unit 310 is managed by the file-associated work management device 110, is shared by one or more folder sharers, and is accessed by the user terminal 120 corresponding to one or more folder sharers among the folder sharers. Manages file list provision and user access rights in the file system in the form of a shared folder.

When the user terminal 120 accesses or attempts to access the shared folder managed by the file-associated task management device 110 , the file system management unit 310 detects the access of the user terminal 120 or a notification signal for this can receive More specifically, the file system manager 310 may receive an access request to the shared folder from the user terminal 120 , and whether to allow the access of the user terminal 120 by checking the access right of the user. can be decided

Alternatively, when the user terminal 120 accesses or attempts to access the shared folder managed by the file-associated task management device 110 , the file system management unit 310 displays a file corresponding to the authority of the user terminal 120 , that is, the corresponding The user terminal 120 may select only files to which the user terminal 120 has the right to access or read and display them to be listed in the file system, or may provide a list of the files.

Here, the file system management unit 310 may obtain user information associated with the user terminal 120 or identification information of the user terminal, and the like, and check the access right to the folder of the user terminal 120 . The file system manager 310 may allow access only when it is confirmed that the user or the user terminal 120 has the right to access the shared folder.

The chat room creation unit 320 may create a file chat room associated with files in one or more shared folders according to a request of the user terminal 120 or the like. Here, the file chat room is a chat room related to a specific file, accessible through the file, and in which a chat message between one or more user terminals 120 for the file and a log message according to the update of the file can be recorded. can be

Alternatively, the chat room creation unit 320 generates a log message by modifying or changing the file based on the right of at least one user of the folder sharers for a specific file, even without a separate file chat room creation request from the user terminal 120 . In the case of requesting a file chat room, inputting a chat message for the corresponding file, or transmitting the input chat message, the file chat room can be created by recognizing this as a file chat room creation request.

Alternatively, for a specific file, if only a general chat room related to the file is opened and used, and a modification or change to the file occurs, the chat room creation unit 320 may switch the file chat room from the general chat room. In general chat rooms, log messages regarding modification of related files cannot be entered or displayed, whereas in file chat rooms, when a file is updated on a shared folder or a file is updated through a chat room, the corresponding file update history is displayed. A log message may be displayed and recorded through the chat window of the file chat room together with the chat message.

The controller 330 may generate a chat file including a message thread to be displayed through the file chat room. The message thread can contain dialog messages and log messages. The chat message is a general chat message input by the user terminal 120 through a chat window of a chat room. A text or image, a voice, or a file object may be input as a conversation message.

The log message is a message indicating the update details when an update event such as modification or change occurs for a file associated with the file chat room, and may be a message displayed through the file chat room.

The controller 330 may create a dialog file object including both the chat message and the log message. Therefore, the message thread included in the chat file object can include both chat messages and log messages. And the chat file object is displayed through the file chat room. Accordingly, in the file chat room materialized in the user terminal 120 , a chat message between one or more folder sharers related to a file and a log message according to a file update generated by one or more folder sharers may be displayed together.

The control unit 330 may collect log messages and chat messages, but may list them in the order of generation. Accordingly, when a log message is generated by updating a file while a chat message is being input, the log message can be inserted between the chat messages. In addition, since the chat message and the log message may be continuously newly generated, the controller 330 may update the chat file object correspondingly in real time.

That is, the chat file object generated by the controller 330 is materialized through the file chat room, and the file chat room is opened through the associated file. A dialog file object includes a message thread, and the message thread can include both a dialog message and a log message.

The controller 330 displays the chat message and the log message together in the file chat room, and the display order is displayed in a time series order or a reverse time series order according to the occurrence time of the message. In addition, the chat message and the log message may be continuously displayed in the chat window whenever they are created.

When the file is not updated for a certain period of time or more, the controller 330 may store the last version of the file most recently updated by the user terminal 120 in the shared folder, and delete the previous version of the file in the order of the oldest. Alternatively, when the control unit 330 selects a file to be deleted first, the file system management unit 310 may delete the file or move it to a separate memory space.

The control unit 330 may check the authority of the user terminal 120 for viewing or updating a file. When the user terminal 120 accesses or requests access to the shared folder or file, the control unit 330 uses the identification information of the user terminal 120 to check the authority of the user corresponding to the user terminal 120 . . In addition, only when it is confirmed that the user terminal 120 has a legitimate right to update the file, it is possible to receive the update details of the file from the user terminal 120 . If the authority is not confirmed, even if the user terminal 120 modifies the file, a corresponding update history may not be generated or may not be received by the file-associated task management device 110 .

Alternatively, the control unit 330 uses the identification information of the user terminal 120 to check the user's authority corresponding to the user terminal 120, and the user terminal 120 confirms that the user terminal 120 has the authority to update the file. In some cases, the update history can be saved or a log message can be generated. If there is no confirmed authority, the contents of the file modified by the corresponding user terminal 120 may be immediately deleted, and a log message is not generated.

In addition, when a new message is generated and accumulated in the file chat room, the controller 330 may provide an alarm for the user terminal 120 . When one or more of a conversation message or a log message is newly generated, the control unit 330 may transmit a notification message to the user terminal 120 of the folder sharer having the right to access the file. Alternatively, the notification message may be transmitted to the user terminal 120 through the network input/output unit 240 .

When a file is updated by one or more folder sharers, the log message management unit 340 generates a log message according to the update details. The log message management unit 340 may receive the update history data from the user terminal 120 that has updated the file or the memory 220 of the file-associated task management device 110 . When the log message is generated, the log message management unit 340 records when and through the user terminal 120 of which folder sharer the corresponding update details are generated, and the log message includes the update details, the subject of the update, the update time, etc. information may be included.

That is, the log message management unit 340 may generate a log message including information on who the shareholder of the folder is who updated the file and specific details of the update history.

Also, the log message management unit 340 may extract a part of the file corresponding to the update details, that is, the updated part of the file together with the log message. And the updated part of the file can be displayed together with the log message in the file chat room. Alternatively, the log message management unit 340 may provide an access path to the final version of the file according to the file update through the file chat room along with the log message.

The chat message manager 350 may generate a chat message by receiving the chat message input from the user terminal 120 . The conversation message may have one or more types of file objects such as text, image, voice, or document. The chat message management unit 350 may also generate a chat message including all of the folder sharers who input the message when, when, and what content when generating the chat message. For this, identification information of the user terminal 120 may be used.

As the chat message of the user terminal 120 is continuously inputted in real time, the chat message management unit 350 also creates a new chat message, and the controller 330 may continuously update the chat file object.

The log message management unit 340 and the chat message management unit 350 may generate related information between the log message and the chat message together when an update history associated with the chat message occurs. That is, when a work instruction is made through a chat message and the file is updated in response to the work instruction, the corresponding log message includes identification information of the chat message related thereto as related information, and the corresponding chat message contains the log message identification information of may be included as related information. Conversation messages and log messages in a relationship can be continuously output together.

On the other hand, a chat message in which the instruction content is not completed by generating a log message may be repeatedly posted or fixed to a specific location at the top or bottom of the chat window of the file chat room.

4 is a flowchart illustrating a file-associated task management method according to an embodiment of the present invention.

First, the file-associated task management apparatus 110 may create a file chat room associated with a specific file in a shared folder (S410).

And the file is updated by the user terminal 120 having the authority to access and update the file (S420). The update of a file may be an example of the update history in which all changes that occur in relation to a file, such as when a file is newly created, modified, changed, or edited, when access rights to the file are changed, etc., occur in the file.

As the file is updated by the user terminal 120 , the file-associated task management apparatus 110 may generate or receive update details ( S430 ). That is, when the user terminal 120 accesses the file stored in the memory 220 in the file-associated task management device 110 through the shared folder and then modifies the file, the user terminal 120 generates an update history. After doing this, it may be transmitted to the file-associated task management device 110 , or the file-associated task management device 110 may directly generate and store the update details.

And the file-associated task management device 110 generates a log message based on the generated update details (S440). According to an embodiment, one log message may be generated for each update detail. Therefore, in this case, when n update details occur, the number of log messages also becomes n.

The file-associated task management apparatus 110 may display a log message through a file chat room (S450). The file-associated task management apparatus 110 may be configured with a message thread including a log message, and may create a chat file object that is provided to the user terminal 120 and can be materialized through a file chat room.

Therefore, as the file-associated task management device 110 provides the chat file object to the user terminal 120 and the chat file object is materialized through the file chat room, a log message that is part or all of the message threads included in the chat file object may be displayed on the user terminal 120 through the file chat room.

Here, if there is a chat message generated before and after the generation of the update details, the file-associated work management apparatus 110 may display the corresponding chat message and the log message together through a chat window in the file chat room. In addition, the chat message and the log message may be mixed and displayed together in one chat window according to a time-series order or a reverse time-series order based on the time of occurrence.

5 is a flowchart illustrating a file-associated task management method according to another embodiment of the present invention.

When the user terminal 120 accesses a file in the shared folder, the file-associated task management apparatus 110 detects the access of the user terminal 120 (S510).

And the file-associated task management device 110 determines whether the user terminal 120 is a user who has the right to read the file (S520). When it is confirmed that the user terminal 120 accessing the file does not have the right to update the file as well as the right to read, the process may be immediately terminated.

In addition, the file-associated task management device 110 may determine whether the user corresponding to the user terminal 120 is a user who has the right to update the file as well as the right to read the file ( S530 ).

That is, through S520 and S530, the file-associated task management device 110 checks whether the user who has accessed the file through the shared folder has the right to read and the right to update the file. As a result of the check, if the user terminal 120 has only the reading right and not the update right, the file-associated work management device 110 opens the file as read-only and provides it for viewing by the user terminal 120 . There is (S545). In this case, it is impossible to update the file by the corresponding user terminal 120 (S555). In this case, even if the user terminal 120 tries to update the file, such as modification or change, it is not applied. It is not transmitted to the type task management device, or even if it is transmitted, the file-linked task management device does not generate a corresponding log message after verifying the authority.

And through S520 and S530, the file-linked task management device 110 checks whether the user has the right to read and update the file, and as a result, the user has the right to read and update the file. In the case of having all of them, the file may be updated by the user terminal 120 corresponding to the user (S540). If the user does not have either the right to view the file or the right to update the file, the process may be terminated.

When the file is updated by the user terminal 120, the file-associated task management apparatus 110 generates a log message corresponding to the update details (S550).

In addition, the file-associated task management apparatus 110 checks whether there is a conversation message generated before and after the file is updated by the user terminal 120 (S560). That is, it is checked whether there is a conversation message input from the user terminal 120 before and after the file update time.

As a result of the check, if there is a chat message generated before and after the file update, a log message is inserted between the corresponding chat messages, and a chat file object including both the chat message and the log message is created ( S570 ).

The file-associated task management device 110 provides the chat file object to the user terminal 120, and the user terminal 120 materializes the chat file object through the file chat room, so that the update details such as modification or change of the file are updated. A message thread including the indicated log message may be displayed (S580).

6 is a flowchart illustrating a file-associated task management method according to another embodiment of the present invention.

According to the embodiment described with reference to FIG. 6 , the file-associated work management device 110 provides a chat message and a log message together through a file chat room, but the chat room badge value according to the number of messages the user has not yet checked can be calculated to provide a chat room badge.

First, the user terminal 120 modifies or changes a file in the shared folder (S610).

Accordingly, when an update history is generated for the file, the file-associated task management apparatus 110 generates a log message corresponding to the update history ( S620 ). In particular, here, the file-associated task management apparatus 110 may automatically create a file chat room when a log message is generated according to the occurrence of an update history, even without a separate request for creating a file chat room from the user terminal 120 . In addition, when the file list is provided, a file chat room related to the file may be displayed together with the file (S630).

Here, the file-associated task management apparatus 110 may calculate a badge value of the file chat room badge and display the chat room badge (S640). The badge value of the file chat room badge may be determined by the number of unconfirmed chat messages or unconfirmed log messages that are not checked or read by the user terminal 120 .

In addition, the file chat room badge may indicate the cumulative number of unconfirmed chat messages and the accumulated number of unconfirmed log messages, respectively.

According to an embodiment, the file chat room badge may consist of two or more badges, and may further include a first badge and a second badge. For example, the first badge may represent the accumulated number of unread chat messages as a chat message badge, and the second badge may represent the accumulated number of unread log messages as a log message badge. In this case, two badges may be provided to the file chat room displayed together with the file list.

Alternatively, according to another embodiment, the file-linked task management device 110 displays the file chat room badge as a single integrated badge, but how the summed badge value is calculated when displaying additional information about the badge value, that is, unconfirmed conversation The number of messages and the number of unacknowledged log messages can be displayed in a separate space. In this case, one badge may be provided to the file chat room displayed together with the file list. In addition, when the file chat room is opened, the number of unconfirmed chat messages and the number of unconfirmed log messages may be separately provided in some space in the file chat room or in a pop-up window.

For example, if the accumulated number of unconfirmed chat messages is 7 and the accumulated number of unconfirmed log messages is 8, and the badge value of the file chat room badge is 15, the file-linked task management device 110 i) the file chat room with the badge value of 15 Provide a badge and separately notify that the cumulative number of unacknowledged chat messages is 7 and the cumulative number of unacknowledged log messages is 8, or ii) a file chat room badge with a badge value of 15, the first badge with a badge value of 7, and a badge value of 8 All of the phosphorus second medium may be provided, or iii) only the first medium having a medium value of 7 and a second medium having a medium value of 8 may be provided, but the embodiment is not limited thereto.

Afterwards, when the file chat room is opened by the request of the user terminal 120 (S650), the file-associated work management device 110 provides the chat file object to be displayed in the file chat room to the user terminal 120 to communicate with the file chat room. You can make the message thread visible. And accordingly, the file chat room badge value may be reset (S660).

When the file chat room badge value is reset, it may mean that the file chat room badge value corresponding to unconfirmed messages opened by the user terminal 120 and checked by the corresponding user becomes 0. Here, the unconfirmed message may include both a conversation message and a log message that the user has not yet confirmed.

Therefore, the file chat room badge is updated when a specific file upload and/or update history including any event such as modification, addition, change, update, etc. occurs, or a new conversation by the folder sharing participants or file sharers of the shared folder. When a message is input, the accumulated number of log messages is counted according to the accumulated number of these update details for the corresponding file, and the accumulated number of newly input conversation messages represents the counted value.

The file-associated task management apparatus 110 may indicate the total of the number of chat messages and log messages that are not read or checked by the specific user terminal 120 among them through the file chat room badge on the user's terminal.

However, it is the file chat room badge value according to the accumulation of log messages in the embodiment of the present invention that indicates the cumulative number of update details that a specific user has not checked, rather than the simple cumulative number of update details due to the above-described events.

Therefore, file chat room badges are recorded differently for each file chat room, as well as separately counted, recorded, and visualized for each user. This is because, when a plurality of users participate in folder sharing, files opened or unopened by each user, read or unread chat rooms, and chat messages and log messages in chat rooms are all different. Accordingly, the file chat room badge may be an indicator for quantifying and displaying matters that one specific user needs to read and check in the future for a specific file chat room.

For example, as a sharing participant who has the authority to update a file applies an update action such as editing or changing, adding a file or memo, etc. to the file, n file update details occur and n unconfirmed log messages are displayed in the file chat room. When accumulated, the badge value of the file chat room badge that is visible to the user becomes n until the user confirms it. Then, when the user opens the corresponding file chat room or the file and reads the newly created and accumulated update history or log message to check all n file update details or n log messages, the file chat room badge that is visualized to the user The badge value of is 0 again.

And when a request signal for opening a file chat room is not input from the user terminal 120 and a new chat message or log message is generated and accumulated without a request for opening a file chat room, the file chat room badge value is 0 It may be continuously accumulated and updated without being reset (S640).

After the file chat room badge is reset, a new chat message or log message may be additionally generated (S670). In this case, the file chat room badge value is accumulated and updated again from 0 (S640). If there is no more input or generation of a new chat message or log message for a preset period of time (S670), a finally updated version of the file may be stored (S680). And as the final version of the file is saved, the previous version of the file may be deleted. The previous version of the file may be deleted according to a request signal for deletion received from the user terminal 120 or according to a preset bar related to deletion.

Although the above has been described with reference to preferred embodiments of the present invention, those skilled in the art can variously modify and change the present invention within the scope without departing from the spirit and scope of the present invention as set forth in the claims below. You will understand that it can be done.

100: File-linked business management system
110: file-linked business management device
120: user terminal
210: processor
220: memory

Claims (14)

a memory and a processor electrically connected to the memory;
the processor
access files in a folder shared by one or more folder sharers;
Opens a file chat room that can be opened through the file as a chat room associated with the file,
Detect generation of a chat message as a work instruction through the file chat room and update of the file according to the work instruction,
When the file is updated, a log message is generated and displayed in the file chat room by using the chat message as related information together with the update history of the file,
When the log message is displayed, a notification message regarding the update of the file is transmitted to the user terminal of the one or more folder sharers,
Wherein the processor opens and uses only a general chat room related to a specific file and does not display the log message, and when the specific file is modified or changed, the general chat room can be switched to the file chat room File-linked business management device. According to claim 1,
the processor is
Receive a conversation message between the one or more folder sharers through the file chat room,
The file-associated task management apparatus of claim 1, wherein the chat message and the log message are displayed together in the file chat room according to an order in which the chat message and the log message are generated. According to claim 1,
the processor
File-linked task management apparatus, characterized in that, through the file chat room, an access path to the final version of the file according to the update of the file together with the log message. According to claim 1,
the processor is
File-linked task management apparatus, characterized in that the file of the last version most recently updated by the user terminal is stored in the folder, and the files of the previous version are deleted in the order of oldest. The method of claim 1,
the processor is
When one or more of the log messages are newly generated, it is checked whether the one or more folder sharers have the right to access the file, and the notification message is transmitted to the user terminal. management device. According to claim 1,
the processor is
The file-linked task management apparatus, characterized in that it generates the log message including information on who the shareholder of the folder that has updated the file is, and specific details of the update details. 7. The method of claim 6,
the processor is
File-linked task management apparatus, characterized in that it includes the updated part of the file as a specific content of the update details. According to claim 1,
The processor displays, as a file chat room badge, the number of log messages that have not yet been read separately from the number of chat messages that have not yet been read by the user terminal in the file chat room.

delete delete delete delete delete delete

Images