Business support system, business support method, and program

Abstract

To make it easy for users to try out an app code.SOLUTION: In a business support system (1), a database code acquisition unit (101) acquires a database code that is an identification code of a database created for business support, a database code setting unit (102) sets the database code in the database, a business support unit (103) executes business support processing for the business support based on the database code, and a request receiving unit (104) receives a request for changing or deleting the database code. The database code setting unit (102) changes or deletes the database code based on the request.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present disclosure relates to a business support system, a business support method, and a program. [Background technology]

[0002] Conventionally, business support systems that manage databases for business support have been known. For example, Non-Patent Document 1 describes a cloud-based business support system that manages apps, which are a type of database. A user of the business support system in Non-Patent Document 1 can set an app code for an app to identify the app. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] "Setting the app code", Internet, searched November 22, 2023, online, https: / / jp.cybozu.help / k / ja / user / app_settings / app_othersettings / appcode.html Summary of the Invention [Problem to be solved by the invention]

[0004] For example, in the business system of Non-Patent Document 1, the record number for identifying a record in an application includes an application code, a hyphen, and a number. When a user posts a post including a record number, the business support system adds a link to the record indicated by the record number to the post. However, in the business system of Non-Patent Document 1, users cannot change or delete application codes, so they cannot easily try out application codes.

[0005] One of the goals of this disclosure is to allow users to easily experiment with app code. [Means for solving the problem]

[0006] A business support system according to one aspect of the present disclosure includes a database code acquisition unit that acquires a database code, which is an identification code for a database created for business support; a database code setting unit that sets the database code in the database; a business support unit that executes business support processing for the business support based on the database code; and a request receiving unit that receives a request to change or delete the database code, and the database code setting unit changes or deletes the database code based on the request. [Effects of the Invention]

[0007] According to the present disclosure, it is possible for users to easily try out application code. [Brief explanation of the drawings]

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Embodiments for Carrying Out the Invention

[0009] [1. Hardware Configuration] An example of an embodiment of a business support system, a business support method, and a program according to the present disclosure will be described. FIG. 1 is a diagram showing an example of the hardware configuration of the business support system. For example, the business support system 1 includes a server 10 and a user terminal 20. Each of the server 10 and the user terminal 20 is connected to a network N such as the Internet or a LAN.

[0010] The server 10 is a server computer. For example, the server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of a volatile memory such as a RAM and a non-volatile memory such as a flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0011] The user terminal 20 is a user's computer. For example, the user terminal 20 is a personal computer, a tablet terminal, or a smartphone. For example, the user terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an operation unit 24, and a display unit 25. The hardware configurations of the control unit 21, the storage unit 22, and the communication unit 23 may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively. The operation unit 24 is an input device such as a mouse or a touch panel. The display unit 25 is a liquid crystal or an organic EL display.

[0012] Note that the programs stored in the storage units 12 and 22 may be supplied via the network N. The hardware configurations of each of the server 10 and the user terminal 20 are not limited to the example of FIG. 1. For example, at least one of the server 10 and the user terminal 20 may include at least one of a reading unit (e.g., a memory card slot) that reads a computer-readable information storage medium and an input / output unit (e.g., a USB terminal) for directly connecting to an external device. A program stored in the information storage medium may be supplied to at least one of the server 10 and the user terminal 20 via at least one of the reading unit and the input / output unit.

[0013] Also, the business support system 1 may include at least one computer. The computer included in the business support system 1 is not limited to the example of FIG. 1. For example, the business support system 1 may include only the server 10. In this case, the user terminal 20 exists outside the business support system 1. The business support system 1 may include the server 10 and another server computer.

[0014] [2. Overview of Business Support System] In the present embodiment, a case where a user uses groupware provided by the server 10 is taken as an example. The groupware is a program for business support. The groupware may be either cloud-based or on-premises. For example, the user registers various data related to the business in the organization to which the user belongs in the database managed by the groupware.

[0015] In the present embodiment, a case where the app of the groupware corresponds to a database is taken as an example. The app has not only the function as a database but also other functions related to business support. For example, the app has at least one of a communication function, a file management function, a mail management function, and other functions. The functions of the app may be known functions. For example, when the user logs in to the groupware and selects an arbitrary app, the user terminal 20 causes the display unit 25 to display an app screen indicating the app.

[0016] FIG. 2 is a diagram showing an example of an app screen. In the present embodiment, as an example of an app, an app for website management will be described. For example, as shown in the upper part of FIG. 2, the app screen SC1 includes a record list L10 showing a list of records which are units of each piece of data in the app. When the user selects an arbitrary record from the record list L10, as shown in the lower part of FIG. 2, the user terminal 20 causes the display unit 25 to display the app screen SC1 showing the details of the record.

[0017] For example, the user can communicate with other users and share files on the app screen SC1 showing the details of a specific record. The user performs his / her own work using various apps taking the app in FIG. 2 as an example. The user can set an app code which is a code for identifying the app in the app. When the user selects the icon I11 for app settings in the state shown in the upper part of FIG. 2, the user terminal 20 causes the display unit 25 to display a setting screen showing the app settings.

[0018] FIG. 3 is a diagram showing an example of a setting screen. For example, as shown in the upper part of FIG. 3, the setting screen SC2 includes an input form F20 for the user to input an app code. In the present embodiment, the user can input any alphanumeric characters in half-width as the app code. If the app code input by the user is not used in other apps, as shown in the lower part of FIG. 3, the user terminal 20 causes a message indicating that the user can use the app code to be displayed near the input form F20.

[0019] For example, when the user selects button B21, an app code is set in the app. When an app code is set in the app, a record number including the app code is set in the records in the app. In this embodiment, the record number includes the app code, a hyphen, and a numerical value for identifying the record. The numerical value after the hyphen indicates the order of the records in the app. For example, in the 61st record in the app "Website Management" with the app code "webkanri", the record number "webkanri-61" is set.

[0020] In this embodiment, when the user makes a post including the record number of a specific record, a link to the record is automatically set in the post. A post is a character string for the user to communicate with other users. A post can also be called a comment, a message, or text. For example, when the user selects a thread for posting, the user terminal 20 causes the display unit 25 to display a thread screen indicating the thread.

[0021] FIG. 4 is a diagram showing an example of a thread screen. For example, as shown in the upper part of FIG. 4, the thread screen SC3 shows the content of the posts made to the thread. The user can input a new post to the input form F30. When the user makes a post including the above-mentioned record number "webkanri-61", as shown in the lower part of FIG. 4, a link to the 61st record in the app "Website Management" with the app code "webkanri" is set in the user's post. When the user selects the link, the user terminal 20 causes the display unit 25 to display an app screen SC1 showing the details of the record.

[0022] As described above, in this embodiment, when a user sets an app code for an app, a link is set to a post that includes a record number corresponding to the app code. For example, if a user is unable to change or delete the app code, the user may not be able to easily try out the app code. For this reason, the business support system 1 allows the user to change or delete the app code so that the user can easily try out the app code.

[0023] FIG. 5 is a diagram showing an example of how a user changes an app code. For example, the user opens the settings screen SC2 of an app for which an app code has been set. As shown in the upper part of FIG. 5, when the user enters the changed app code (new app code) in input form F20 and selects button B21, the app code of the app is changed. In this embodiment, when the user changes the app code, a link is no longer set in posts that include the record number of the app code before the change, as shown in the lower part of FIG. 5.

[0024] FIG. 6 is a diagram showing an example of how a user deletes an app code. For example, the user opens the settings screen SC2 of an app for which an app code has been set. As shown in the upper part of FIG. 6, when the user deletes the app code displayed in the input form F20 and selects button B21, the app code for that app is deleted. In this embodiment, when the user deletes the app code, a link is no longer set in the post that includes the record number of the deleted app code, as shown in the lower part of FIG. 6.

[0025] As described above, the business support system 1 has a configuration for changing application code and a configuration for deleting application code. In this embodiment, a case will be described in which the business support system 1 has both a configuration for changing application code and a configuration for deleting application code. However, the business support system 1 may have only one of the configurations for changing application code or the configuration for deleting application code. The configuration for changing application code and the configuration for deleting application code will be described in detail below.

[0026] [3. Functions realized by the business support system] FIG. 7 is a diagram showing an example of functions realized by the business support system 1. As shown in FIG.

[0027] [3-1. Functions realized by the server] For example, the server 10 includes a data storage unit 100, an application code acquisition unit 101, an application code setting unit 102, a business support unit 103, and a request reception unit 104. Each unit in the data storage unit 100 is realized by the storage unit 12. Each unit in the application code acquisition unit 101, the application code setting unit 102, the business support unit 103, and the request reception unit 104 is realized by the control unit 11.

[0028] [Data storage section] The data storage unit 100 stores various data for business support. For example, the data storage unit 100 stores an application database DB1 indicating various data of applications and a thread database DB2 indicating various data of threads.

[0029] Fig. 8 is a diagram showing an example of the application database DB1. For example, the application database DB1 stores application IDs, which are IDs for identifying applications, setting data indicating specific settings of the applications, and record data indicating details of records in the applications. The application database DB1 may store any data, and the data stored in the application database DB1 is not limited to the example shown in Fig. 8. For example, the application database DB1 may store a history of setting data.

[0030] For example, when a user creates a new application, the server 10 issues an application ID for the application. The application ID is an ID for the business support system 1 to internally identify the application. The method of creating the application may be a known method. For example, the user may create a no-code or low-code application, or may create an application that requires a certain amount of code input. The server 10 associates the setting data indicating the settings specified by the user and the record data indicating the records created in the new application with the application ID of the new application and stores them in the application database DB1. Instead of the user creating the application himself / herself, default applications may be prepared. The application database DB1 may store data of default applications.

[0031] For example, the setting data indicates the setting content specified by the user. In the present embodiment, the setting data of an application with an application code set indicates the application code. The setting data of an application without an application code set does not indicate the application code. The setting data may indicate other settings other than the application code. For example, the setting data may be the name of the application, the setting of fields in the application, a memo for the administrator of the application, the display format of the record list L10, the setting of the graph displayed in the application, the icon of the application, the access authority, or other settings. When the user changes the settings of a certain application, the server 10 changes the setting data of the application.

[0032] For example, record data indicates the values of each field of a record in an app, the comments registered in the record, or the files registered in the record. The record data may indicate all or part of the path (e.g., URL) for displaying the record (e.g., only the argument part of the URL). The record data may be managed in a database different from the setting data. When the user creates a new record, the server 10 adds record data indicating the new record to the app database DB1. When the user changes the content of a record, the server 10 changes the record data of the record. When the user deletes a record, the server 10 deletes the record data of the record.

[0033] In this embodiment, the record data of an app for which an app code is set indicates a record number that is a combination of the app code, a hyphen, and the numerical value of each individual record. The record number of a record in a certain app is different from the record numbers of other records in that app. The record number of a record in a certain app is also different from the record numbers of records in other apps. The server 10 can uniquely identify a record by the record number. When the user sets an app code for the app, a record number is added to the record data. The record data of an app for which no app code is set shall include a numerical value for identifying each individual record.

[0034] FIG. 9 is a diagram showing an example of the thread database DB2. For example, the thread database DB2 stores a thread ID that is an ID for identifying a thread and post data indicating a post to the thread. Any data may be stored in the thread database DB2, and the data stored in the thread database DB2 is not limited to the example of FIG. 9. For example, the thread database DB2 may store the user ID of the user who made the post, the posting date and time, and data on reactions to the post, etc.

[0035] For example, when a user creates a new thread, server 10 issues a thread ID for the thread. When a new post is made to the thread, server 10 stores, in thread database DB2, post data indicating details of the post, associated with the issued thread ID. The post data may include not only text indicating the content of the post, but also other data such as attached files included in the post. In the present embodiment, the link of the post including the record number is dynamically set at the time of display, but the post data may be stored in thread database DB2 with a link set in advance for the post.

[0036] Note that the data stored in data storage unit 100 is not limited to the above example. Data storage unit 100 can store any data. For example, data storage unit 100 may store a user database in which various user data is stored. The user database stores data such as user IDs and passwords for groupware login. Data storage unit 100 may store data for each screen such as application screen SC1, setting screen SC2, or thread screen SC3.

[0037] [Application Code Acquisition Unit] Application code acquisition unit 101 acquires an application code, which is a code for identifying an application created for business support. In the present embodiment, unlike the name of the application, application code acquisition unit 101 does not acquire a code automatically generated by business support system 1, but acquires an application code input by the user. For example, when the user inputs an application code into input form F20 on setting screen SC2 and selects button B21, user terminal 20 transmits the application code input by the user to server 10. Application code acquisition unit 101 acquires the application code from user terminal 20. When another computer other than server 10 mediates communication between server 10 and user terminal 20, application code acquisition unit 101 may acquire the application code via the other computer.

[0038] Note that the user does not have to input the application code. For example, the application code acquisition unit 101 may acquire the application code by automatically generating the application code. The application code acquisition unit 101 may generate a random character string as the application code, or may generate the application code string based on a predetermined rule. The application code acquisition unit 101 may acquire the application code when the user performs an operation for setting the application code to an already created application, or may acquire the application code at the time of creating the application. When the user changes the application code, the application code acquisition unit 101 acquires the changed application code. The application code acquisition unit 101 may acquire an application code that is the same character string as the name of the application. For example, the name of the application may start with an alphabet and be alphanumeric in half-width, and the application code may also be the same alphanumeric in half-width.

[0039] [Application Code Setting Unit] The application code setting unit 102 sets the application code to the application. The application code setting unit 102 setting the application code means that the application code setting unit 102 adds the application code to the application database DB1. In the present embodiment, the application code setting unit 102 sets the application code to the application by associating the application code with the application ID of the application to which the application code is to be set. In the example of the application database DB1 in FIG. 8, the application code setting unit updates the setting data so that the setting data associated with the application ID indicates the application code. For example, when the user inputs the application code in the input form F20 of the setting screen SC2 and selects the button B21, the application code setting unit 102 sets the application code to the application.

[0040] In this embodiment, when a request unit (to be described later) receives a request (to be described later), the application code setting unit 102 changes or deletes the application code based on the request. For example, when a user inputs a changed application code into the input form F20 on the setting screen SC2 of a certain application and selects the button B21, the application code setting unit 102 changes the application code of the application. Changing the application code can also be referred to as overwriting or updating the application code. The changed application code is an application code in which all or part of the application code before the change is different.

[0041] For example, when a user deletes the application code in the input form F20 on the setting screen SC2 of a certain application and selects the button B21, the application code setting unit 102 deletes the application code of the application. Changing from a state where an application code is set for the application to a state where no application code is set for the application corresponds to deleting the application code. The application code setting unit 102 deletes the application code indicated by the setting data associated with the application ID from the application database DB1. Note that an image or text for deleting the application code may be displayed on the setting screen SC2. When the user selects the image or the text, the application code setting unit 102 may delete the application code.

[0042] [Business Support Department] The business support department 103 executes business support processing for business support based on the application code. The business support processing is processing executed based on the application code. The business support processing may be any processing related to business support. In this embodiment, an example is given where setting a link for a post corresponds to the business support processing, but the business support processing may be other processing other than setting the link. For example, the business support processing may be searching for an application executed based on the application code, searching for a record executed based on the application code, or other processing. That is, the application code may be used as an index at the time of searching for an application. The record number may be used as an index at the time of searching for a record.

[0043] For example, the business support department 103 determines whether a submission to the business support system 1 includes an app code. In the present embodiment, the case where this determination is made at the time of displaying the submission is taken as an example, but this determination may be made at any timing. For example, this determination may be made at the time of submission. When a new submission is made, the business support department 103 may determine whether the submission includes an app code. When it is determined that the submission includes an app code, the business support department 103 may set a link to the submission and store the submission data in the thread database DB2. That is, at the time when the submission is made, the submission data may include a link.

[0044] For example, when a user requests the display of a submission, the business support department 103 determines, based on the app database DB1, whether the submission includes an app code of any app. When it is determined that a submission includes an app code, the business support department 103 sets a link to the app in the submission. The method of setting the link may be a known method. For example, the business support department 103 sets a link in the submission using tags of a markup language such as HTML. In the present embodiment, the case where the business support department 103 sets a link to a specific record in the app in the submission is taken as an example, but the business support department 103 may set a link to the entire app (for example, a link to the upper app screen SC1 in FIG. 2) in the submission.

[0045] For example, the business support department 103 determines whether a submission includes a combination of an app code, a specific symbol, and information for identifying a record in the app. When it is determined that the submission includes the combination, the business support department 103 may set a link to the record in the app in the submission. In the present embodiment, the record number corresponds to the combination. Therefore, the record number and the described location can be read as the combination. The combination may be any criterion for determining whether to set a link. The combination is not limited to the record number. For example, a number may not be used in the combination.

[0046] The specific symbol included in the above combination is a symbol that can identify that the business support department 103 is a record number. In this embodiment, a hyphen corresponds to the specific symbol. The specific symbol may be any symbol that serves as a mark for the record number. The specific symbol is not limited to a hyphen. For example, the specific symbol may be another symbol such as a plus, minus, or at sign. The information for identifying a record is also not limited to the numerical values of this embodiment. The information for identifying a record may be a character or other symbol. When the information for identifying a record is a numerical value, it does not have to be numbered consecutively for each record. The numerical value can start from any value. For example, the numerical value of the first record of a certain application may be another value such as 0 instead of 1.

[0047] In the example of FIG. 4, when the business support department 103 receives a thread display request from a certain user terminal 20, it determines whether any post of the thread contains the record number of any application based on the application database DB1 and the thread database DB2. This determination is executed by string matching. If there is no post containing the record number of any application, the business support department 103 does not set a link. When there is a post containing the record number of any application, the business support department 103 sets a link. When there are multiple posts to be displayed, the business support department 103 executes the above determination for each of the multiple posts.

[0048] In this embodiment, when the application code (in this embodiment, the post containing the record number) is changed or deleted after a post containing the application code is made, the business support department 103 does not set a link to the application for the post. When the application code has not been changed or deleted after a post containing the application code (in this embodiment, the post containing the record number) is made, the business support department 103 sets a link to the application for the post.

[0049] In addition, the Business Support Department 103 may set a link for a post made outside of a thread. For example, the Business Support Department 103 may set a link for a comment in an app, a message in a chat, a comment on a bulletin board, a post included in a notification, or other posts. The Business Support Department 103 may determine whether to set a link for these posts by determining whether they include a record number.

[0050] Also, the order of the app code and the like in the record number is not limited to the example of this embodiment. For example, the record number may be arranged in the order of a specific symbol, an app code, and information for identifying a record. Further, the record number may include only an app code and information for identifying a record without including a specific symbol such as a hyphen. The Business Support Department 103 may set a link to the app indicated by the app code for a post that includes only the app code without including the record number. In this case, it may not be necessary to assign a record number to each record.

[0051] [Request Reception Department] The Request Reception Department 104 receives a request for changing or deleting an app code. The request is data in a predetermined format indicating the change or deletion of the app code. For example, when a user performs an operation for changing or deleting an app code on the setting screen SC2, the user terminal 20 transmits a request for changing or deleting the app code to the server 10. The Request Reception Department 104 receives the request from the user terminal 20. It is assumed that the request includes the app code to be changed or deleted. Further, when a change to the app code is requested, it is assumed that the request includes the app code after the change. When the Request Reception Department 104 receives the request, the process by the App Code Setting Department 102 is executed.

[0052] [3-2. Functions Realized by User Terminal] For example, the user terminal 20 includes a data storage unit 200, a display control unit 201, and an operation reception unit 202. The data storage unit 200 is realized by a storage unit 22. Each of the display control unit 201 and the operation reception unit 202 is realized by a control unit 21.

[0053] [Data storage unit] The data storage unit 200 stores data for business support. For example, the data storage unit 200 stores a browser for displaying various screens of the business support system 1. For example, the data storage unit 200 stores a program dedicated to the business support system 1.

[0054] [Display control unit] The display control unit 201 causes various screens in the business support system 1 to be displayed on the display unit 25. For example, the display control unit 201 causes various screens such as an application screen SC1, a setting screen SC2, or a thread screen SC3 to be displayed on the display unit 25 based on the data received from the server 10.

[0055] [Operation reception unit] The operation reception unit 202 receives various operations in the business support system 1. For example, it receives operations on various screens such as an application screen SC1, a setting screen SC2, or a thread screen SC3. The data indicating the operation content received by the operation reception unit 202 is appropriately transmitted to the server 10.

[0056] [4. Processes executed in the business support system] Next, as an example of the processes executed in the business support system 1, an application code process for setting an application code and a thread process for displaying a thread will be described. The control units 11 and 21 execute the programs stored in the storage units 12 and 22 respectively, thereby executing the application code process and the thread process. The application code process and the thread process are examples of the processes of the business support method of the present embodiment.

[0057] [4-1. Application code process] FIG. 10 is a diagram showing an example of application code processing. As shown in FIG. 10, when the user selects the icon I11 while the application screen SC1 of a certain application is displayed, the user terminal 20 executes a process for displaying the setting screen SC2 of the application between the server 10 (S100). In S100, the server 10 refers to the application database DB1 and acquires the setting data of the application selected by the user. The server 10 generates display data (e.g., HTML data) of the setting screen SC2 based on the acquired setting data. The server 10 transmits the display data of the setting screen SC2 to the user terminal 20.

[0058] The user terminal 20 identifies the user's operation on the setting screen SC2 based on the signal detected by the operation unit 24 (S101). In S101, it is assumed that an operation for setting the application code, an operation for changing the application code, or an operation for deleting the application code is performed. In the example of FIG. 3, the operation for setting the application code is an operation in which the user inputs the application code into the input form F20 and selects the button B21. In the example of FIG. 5, the operation for changing the application code is an operation in which the user inputs the changed application code into the input form F20 and selects the button B21. In the example of FIG. 6, the operation for deleting the application code is an operation in which the user deletes the application code in the input form F20 and selects the button B21. When other operations are performed, a process corresponding to the other operation is executed between the server 10 and the user terminal 20, and the application code processing ends.

[0059] In S101, when the user performs an operation for setting the app code (S101: Setting), the user terminal 20 sends the app code entered by the user to the server 10 (S102). The server 10 acquires the app code from the user terminal 20 (S103). The server 10 sets the app code entered by the user for the app selected by the user (S104), and the app code process ends. In S104, the server 10 associates the app code entered by the user with the app ID of the app being set by the user and stores it in the app database DB1.

[0060] In S101, when the user performs an operation for changing the app code (S101: Change), the user terminal 20 sends the changed app code entered by the user to the server 10 (S105). In S105, the user terminal 20 can also send a change request for changing the app code. The server 10 acquires the changed app code from the user terminal 20 (S106). In S106, the server 10 can also receive a change request from the user terminal 20. The server 10 changes the app code of the app selected by the user (S107), and the app code process ends. In S107, the server 10 changes the app code associated with the app ID of the app being set by the user and stored in the app database DB1 to the app code acquired in S106.

[0061] In S101, when the user performs an operation for deleting the app code (S101: Delete), the user terminal 20 sends a deletion request for deleting the app code to the server 10 (S108). The server 10 receives the deletion request from the user terminal 20 (S109). The server 10 deletes the app code of the app selected by the user (S110), and the app code process ends. In S110, the server 10 deletes the app code associated with the app ID of the app being set by the user from the app database DB1.

[0062] [4-2. Thread Processing] FIG. 11 is a diagram showing an example of thread processing. As shown in FIG. 11, when a user selects a thread, the user terminal 20 sends a display request for displaying the thread to the server 10 (S200). Assume that the display request includes the thread ID of the thread to be displayed. The server 10 receives the display request for the thread (S201). The server 10 determines whether the post of the thread to be displayed includes a record number based on the application database DB1 and the thread database DB2 (S202).

[0063] In S202, if it is determined that the post of the thread to be displayed includes a record number (S202: Y), the server 10 sets a link to the post including the record number (S203). In S203, the server 10 embeds a link in the post including the record number using an HTML tag or the like. Assume that the data necessary for generating the link (for example, all or part of the URL) is stored in the application database DB1. In S202, if it is determined that the post of the thread to be displayed does not include a record number (S202: N), the process of S203 is not executed.

[0064] The server 10 executes a process for displaying the thread screen SC3 between the server 10 and the user terminal 20 (S204). In S204, the server 10 generates display data (for example, HTML data) of the thread screen SC3 and sends it to the user terminal 20. If the process of S203 is executed, the display data of the thread screen SC3 includes a link. The user terminal 20 identifies a user operation on the thread screen SC3 (S205). In S205, assume that an operation where the user makes a new post or an operation where the user selects a link set in the post is performed. If another operation is performed, a process corresponding to the other operation is executed between the server 10 and the user terminal 20, and the thread processing ends.

[0065] In S205, when the user makes a new post (S205: New Post), the user terminal 20 executes a process for registering the new post in the thread database DB2 with the server 10 (S206), and the thread process ends. When the user makes a new post including a record number, the new post including the record number is registered in the thread database DB2. In S205, when the user performs an operation of selecting a link set for the post (S205: Link Selection), the user terminal 20 executes a process for displaying the application screen SC1 indicating the record indicated by the link with the server 10 (S207), and the thread process ends.

[0066] [Summary of Embodiment] When the business support system 1 of the present embodiment receives a request for changing or deleting an application code, it changes or deletes the application code based on the request. As a result, the user can easily try the application code. For example, the user can change the application code that has been set once to a more user-friendly application code. When the application code of an application is changed, the user can set the application code before the change for another application. The user can delete the application code when the application code that has been set once is not as intended. When the application code of an application is deleted, the user can set the deleted application code for another application. For example, the user can also easily try whether the application code is actually useful for their business. For example, the business support system 1 can prevent a situation where a user who knows the existence of the application code but is considering setting it to try the function of the link hesitates because they cannot determine an appropriate application code. For example, if the user first sets an application code but the role of the application changes due to changes in business operations or the like, the user can change the application code according to the actual situation to make it clear to other users what kind of application it is. For example, if the user tries to set an application code thinking that it can be used as a record numbering function but the setting of the application code becomes unnecessary, the user can also delete the entire application code setting.

[0067] In addition, different from the name of the application, the business support system 1 acquires the application code input by the user, rather than the code automatically generated by the business support system 1. Thereby, since the business support system 1 can make the user input an application code according to the user's preference, the convenience of the user can be improved.

[0068] In addition, when it is determined that a post to the business support system 1 includes an application code, the business support system 1 sets a link to the application in the post. Since the user does not need to paste a link to their own post, the business support system 1 can improve the convenience of the user. The user can easily set a link to their own post. For example, when the user writes the link of a record of an application in the comment of another application, the user only needs to input the record number including the application code, so the business support system 1 can improve the convenience of the user.

[0069] In addition, the business support system 1 determines whether a post includes a combination of an application code, a specific symbol, and information for identifying a record in the application. When it is determined that a certain post includes the combination, the business support system 1 sets a link to the record in the application indicated by the combination in the post. Thereby, the business support system 1 can surely identify whether a link should be set in the post. For example, the business support system 1 can prevent a link from being mistakenly set to the same English word as a certain application code due to a specific symbol or the like.

[0070] In addition, when the application code is changed or deleted after a post including the application code is made, the business support system 1 does not set a link to the application in the post, and when the application code has not been changed or deleted after the post is made, the business support system 1 sets a link to the application in the post. Thereby, the business support system 1 can prevent a situation where the link remains in the post forever even though the application code has been changed or deleted.

[0071] [6. Modification Example] Note that the present disclosure is not limited to the embodiments described above. The present disclosure can be appropriately modified without departing from the gist of the present disclosure.

[0072] FIG. 12 is a diagram showing an example of functions realized by the business support system 1 of the modification example. As shown in FIG. 12, in the modification example described hereinafter, the server 10 includes an acquisition request reception unit 105, a transmission unit 106, a restriction unit 107, a release unit 108, and a similar notification unit 109. Each of the acquisition request reception unit 105, the transmission unit 106, the restriction unit 107, the release unit 108, and the similar notification unit 109 is realized by the control unit 11.

[0073] [6-1. Modification Example 1] For example, when a post (a post including a record number in the example of the embodiment) including a certain application code is made and then the application code is changed or deleted, even if the application code is set in another application, the post may not be set with a link to the other application. In the examples of FIGS. 3 to 5, the application code of the application "Website Management" has been changed from "webkanri" to "webmanagement". In the example of FIG. 6, the application code "webkanri" has been deleted. In these cases, even if the application code "webkanri" is set in another application, the posts in FIGS. 4 to 6 may not be linked to the other application.

[0074] In Modification Example 1, the setting data stored in the application database DB1 indicates the setting date and time of the application code. For example, when the application code setting unit 102 sets an application code for a certain application, the setting data is updated so that the current date and time is shown as the setting date and time indicated by the setting data. Also, the post data stored in the thread database DB2 indicates the post date and time which is the date and time when the post was made. For example, when a certain post is made, the server 10 generates the post data so that the current date and time is shown as the post date and time indicated by the post data.

[0075] For example, when a certain post contains an app code, the Business Support Department 103 determines whether the posting date and time of the post is after the setting date and time of the app code. If the posting date and time is after the setting date and time, the Business Support Department 103 sets a link to the app indicated by the app code in the post. If the posting date and time is before the setting date and time, the Business Support Department 103 does not set a link to the app indicated by the app code in the post. Thereby, even if the app code is changed or deleted after the post, and the app code is set to another app, a link to the other app is not set in the post.

[0076] Note that the control for the Business Support Department 103 not to set a link to another app in a post containing an app code that has been changed or deleted is not limited to the above example. For example, at the time of posting a post containing a certain app code, the Business Support Department 103 may set a link to the app indicated by the app code in the post so that even if the app code is later set to another app, a link to the other app is not set in the post. For another example, when a certain app code is changed, the Business Support Department 103 may change the part of the app code before the change to the app code after the change in the posts containing the app code before the change so that a link to another app is not set in the post. When a certain app code is deleted, the Business Support Department 103 may delete the part of the app code that has been deleted in the posts containing the app code before the change so that a link to another app is not set in the post.

[0077] In Modification Example 1, when the application code of a certain application is changed or deleted, the application code before the change or the deleted application code is set for another application. For example, when the user inputs the application code before the change or the deleted application code in the input form F20 of the setting screen SC2 of another application and selects the button B21, the application setting unit sets the application code before the change or the deleted application code for another application. When it is determined that a post made after the application code is set for another application by the business support unit 103 of Modification Example 1 contains the application code, a link to another application is set for the post.

[0078] Suppose that after the application code "webkanri" of the application "Website Management" in FIGS. 2 and 3 is changed or deleted, the same application code "webkanri" is set for another application "Web Marketing Management". Suppose that after this, the user makes a post including the record number "webkanri-10". In this case, the business support unit 103 sets a link to the 10th record of another application "Web Marketing Management" instead of the application "Website Management" for the post. For example, since the posting date and time of the post is after the setting date and time when the application code "webkanri" is set for another application "Web Marketing Management", the business support unit 103 sets a link to another application "Web Marketing Management" for the post.

[0079] When the application code is changed or deleted after a post including the application code is made, the business support system 1 of Modification Example 1 does not set a link to another application for the post even if the application code is set for another application. When it is determined that a post made after the application code is set for another application contains the application code, the business support system 1 sets a link to another application for the post. Thereby, the business support system 1 can effectively utilize the application code that has become unused due to the change or deletion. The business support system 1 can prevent a situation where a link to another application is set for a post made before the change or deletion of the application code.

[0080] [6-2. Modification Example 2] For example, in the embodiment, an example was given in which when the application code of a certain application is changed or deleted, the link to the application is not set for a post including the application code before the change or the deleted application code. In Modification Example 2, an example in which the link to the application is set for the post is given. In the examples of FIGS. 3 to 6, the application code "webkanri" of the application "Website Management" is changed or deleted. In this case, instead of the link not being set for the post in FIG. 4 (the post including the record number "webkanri-61") made before the change or deletion of the application code "webkanri", the same link as the originally valid link (the link to the 61st record of the application "Website Management") is set.

[0081] Even if the application code of a certain application is changed after a post including the application code is made, the business support unit 103 in Modification Example 2 sets a link to the application for the post including the application code before the change. For example, in Modification Example 2, the setting data stored in the application database DB1 shows the history of the application code. The history shows the application code before the change, the deleted application code, the date and time of the change of the application code, the date and time of the deletion of the application code, or a combination thereof. The history may show the setting date and time of the application code before the change or the setting date and time of the deleted application code. Similar to Modification Example 1, the post date and time is shown in the post data of the thread database DB2.

[0082] For example, when a certain post contains an app code before modification or a deleted app code, the Business Support Department 103 compares the posting date and time of the post with the modification date and time or deletion date and time of the app code. If the posting date and time of the post is after the modification date and time or the deletion date and time, the Business Support Department 103 does not set a link to the app indicated by the app code before modification or the deleted app code in the post. If the posting date and time of the post is before the modification date and time or the deletion date and time, the Business Support Department 103 sets a link to the app indicated by the app code before modification or the deleted app code in the post.

[0083] Note that when the Business Support Department 103 sets a link at the time of posting, even if the app code is modified after a post containing the app code of a certain app is made, without using the modification date and time, deletion date and time, and posting date and time, a link to the app may be set in the post containing the app code before modification. By setting a link to the app for which the app code was set at the time the post was received, the process for the Business Support Department 103 to set a link when the post is displayed becomes unnecessary.

[0084] Even if the app code is modified after a post containing the app code of a certain app is made, the Business Support System 1 of Modification Example 2 sets a link to the app in the post containing the app code before modification. Thereby, the Business Support System 1 can prevent the link of the post where the link was originally set from becoming invalid.

[0085] [6-3. Modification Example 3] For example, in Modification 2, even if the application code of a certain application is set to another application after the application code is changed, the business support department 103 may set a link to the application in a post that includes the application code before the change (a post made before the change). After the application code of a certain application is changed, if the application code is set to another application and a new post including the application code is made, the business support department 103 sets a link to the other application in the post. The control of these links may be the same as the control described in Modifications 1 and 2. That is, the business support department 103 may control the setting of the link according to the setting time of the application code, etc., or may set the link at the time of posting.

[0086] In the business support system 1 of Modification 3, even if the application code is set to another application after the application code is changed, a link to the application is set in a post that includes the application code before the change. Thereby, the business support system 1 can prevent the link of a post where the link was originally set from becoming invalid. The business support system 1 can prevent a link to another application that the user who made the post did not intend from being set.

[0087] [6-4. Modification 4] For example, when the business support system 1 cooperates with another business support system, when a post including the application code is made in the other business support system, a link to the application managed by the business support system 1 may be set in the post. The business support system 1 is communicably connected to another business support system via the network N. For example, the other business support system may be groupware or a system for managing shared mail. The other business support system may be a system that supports the user's business by a program different from that of the business support system 1.

[0088] The business support system 1 of Modification Example 4 includes an acquisition request reception unit 105 and a transmission unit 106. The acquisition request reception unit 105 can receive an acquisition request for an app code from another business support system. The acquisition request for the app code is transmitted from another business support system to the business support system 1 in a predetermined data format. The acquisition request can also be regarded as a request for another business system to obtain a link corresponding to the app code. The acquisition request may include an app code corresponding to the link to be acquired. For example, when a user posts a message including an app code in another business support system, the other business support system transmits an acquisition request including the app code to the business support system 1. The acquisition request reception unit 105 receives the acquisition request from the other business support system. Note that the acquisition request may include other information (e.g., app name) that enables the business support system 1 to identify the app instead of the app code.

[0089] When an acquisition request is received, the transmission unit 106 transmits information on a combination of an app code and a link corresponding to the app code to another business support system. The method for acquiring the link may be the same as in the embodiment. The transmission unit 106 identifies the app to which the link should be transmitted based on the acquisition request and generates a link to the app. Another business support system sets a link to the user's post based on the information transmitted by the transmission unit 106. The method for setting the link by another business support system may be the same as the method for setting the link by the business support system. Another business support system includes the link transmitted by the transmission unit 106 in the user's post. When the link is selected in another business support system, access to a specific record of the app indicated by the link occurs.

[0090] In addition, when an app code is set for a certain app, the transmission unit 106 may transmit the app code to other business support systems. For example, when the app code of a certain app is changed or deleted, the transmission unit 106 may transmit the changed app code to other business support systems, or may transmit a notification indicating that the app code has been deleted.

[0091] In other business support systems, when it is determined that a post to another business support system includes an app code, a link to the app may be set for the post. The method of setting the link for the post may be the same as that of the business support system 1. For example, other business support systems store a database in which the same app IDs and setting data as those stored in the app database DB1 are stored. When displaying a post made to the other business support system, the other business support system may execute the same processing as that of the business support unit 103 based on the database to set a link for the post. The other business support system may set a link for the post when the post is made to the other business support system. The processing in this case may also be executed by the same processing as the processing described as the processing of the business support unit 103.

[0092] For example, assume that another business support system supports a user's business by managing shared emails in the organization to which the user belongs. Assume that user ID linkage is performed between the business support system 1 and the other business support system. A common user ID may be used between the business support system 1 and the other business support system. In this case, when a post including the app code of the app of the business support system 1 is made using the comment function of the shared email, the other business support system may set a link to the app for the post. When the user selects the link in the other business support system, the user terminal 20 accesses the app.

[0093] When the business support system 1 of Modification Example 4 receives an acquisition request from another business support system, it transmits information on a combination of an application code and a link corresponding to the application code. Thereby, the business support system 1 can improve the convenience for users who use other business support systems. Note that the business support system 1 of Modification Example 4 does not necessarily have a configuration for changing or deleting the application code. For example, the business support system 1 may set an application code that cannot be changed or deleted by the user in the application and notify the other business support systems of the application code.

[0094] [6-5. Modification Example 5] For example, when a user changes or deletes the application code of a certain application, the user may want to restore the application code before the change or the deleted application code. If the application code before the change or the deleted application code is set in another application, the user cannot restore it. Therefore, the application code before the change or the deleted application code may not be set in another application.

[0095] The business support system 1 of Modification Example 5 includes a restriction unit 107. The restriction unit 107 restricts the application code from being set in another application when the application code of a certain application is changed or deleted. For example, the data storage unit 100 stores a restriction database indicating application codes whose settings in other applications are restricted. The restriction database stores an application ID and an application code to be restricted. The application code to be restricted is set only in the application with the application ID associated with the application code.

[0096] For example, when the application code of a certain application is changed or deleted, the restriction unit 107 stores the application code in the restriction database. When the application code is input on the setting screen SC2 of an application other than the application with the application ID associated with the application code, the restriction unit 107 displays an error message to prevent the application code from being set in other applications.

[0097] In Modification Example 5, the application code setting unit 102 sets an application code that is not restricted by the restriction unit 107 for the application. The application code setting unit 102 does not set an application code that is restricted by the restriction unit 107 for the application. However, the application code setting unit 102 may set the application code for the application in which the application code was originally set. That is, the application code setting unit 102 may set the application code for the application indicated by the application ID associated with the application code stored in the restriction database.

[0098] The business support system 1 of Modification Example 5 restricts the setting of an application code for another application when the application code is changed or deleted. Thereby, the business support system 1 can prevent the user from being unable to restore the application code before the change or the deleted application code. Since the user can restore the originally set application code, the business support system 1 can improve the convenience for the user.

[0099] [6-6. Modification Example 6] For example, in Modification Example 5, when the number of application codes restricted by the restriction unit 107 increases, even if the user tries to set an application code for a new application, the options for the character string that can be specified as the application code decrease. Therefore, in Modification Example 6, a case where the restriction on the application code restricted by the restriction unit 107 is released under a predetermined condition will be described. The release of the restriction on the application code means permitting the setting of the application code by the application code setting unit 102.

[0100] The business support system 1 of Modification Example 6 includes a release unit 108. The release unit 108 releases the restriction on the application code by the restriction unit 107 based on a predetermined condition. The predetermined condition is a condition serving as a criterion for whether to release the restriction on the application code. The predetermined condition may be any condition. For example, the predetermined condition may be that a predetermined period has elapsed since the restriction on the application code, the user performs an operation to release the application code, the application code is changed a predetermined number of times, or the application is deleted. The release unit 108 may determine whether these predetermined conditions are satisfied.

[0101] In Modification Example 6, take the case where the elapse of a predetermined period since the restriction on the application code corresponds to the predetermined condition as an example. In Modification Example 6, the restriction database stores the date and time when the setting of the application code was restricted by the restriction unit 107, or the date and time after a predetermined time from the said date and time (that is, the date and time when the restriction by the restriction unit 107 is released). The release unit 108 determines whether a predetermined period has elapsed since the restriction on the application code based on the current date and time and the date and time stored in the restriction database. If it is determined that a predetermined period has not elapsed since the restriction on the application code, the release unit 108 does not release the restriction by the restriction unit 107, and if it is determined that a predetermined period has elapsed since the restriction on the application code, the release unit 108 releases the restriction by the restriction unit 107.

[0102] The business support system 1 of Modification Example 6 releases the restriction on the application code by the restriction unit 107 based on a predetermined condition. Thereby, the business support system 1 can prevent the situation that an application code that is no longer used cannot be set for other applications. The business support system 1 can prevent the number of options of the character string that the user can specify as the application code from decreasing.

[0103] [6-7. Modification Example 7] For example, in an embodiment, when there is an app code that is the same as the app code input by the user on the setting screen SC2, a predetermined message may be displayed on the setting screen SC2. When the user tries to set an app code that is similar to another app code, there is a possibility that a link to another app may be set due to an input error during posting, so a message to that effect may be displayed on the setting screen SC2.

[0104] The business support system 1 of Modification Example 7 includes a similarity notification unit 109. The similarity notification unit 109 notifies the user that the app code is similar to another app code when the app code is similar to another app code. Similarity means that the same characters are present for a predetermined number of characters or more, or that the same characters are present for a predetermined ratio or more. For example, when the user inputs an app code into the input form F20, the similarity notification unit 109 acquires the app code from the user terminal 20 before the user selects the button B21.

[0105] For example, the similarity notification unit 109 refers to the app database DB1 and determines whether there is an app code similar to the app code input by the user. When it is determined that there is an app code similar to the app code input by the user, the similarity notification unit 109 transmits data indicating that there is an app code similar to the app code input by the user to the user terminal 20. When the user terminal 20 receives the data from the server 10, the user terminal 20 causes a message indicating that there is an app code similar to the app code input by the user to be displayed on the setting screen SC2.

[0106] For example, when it is determined that there is no app code similar to the app code input by the user, the similarity notification unit 109 transmits data indicating that there is no app code similar to the app code input by the user to the user terminal 20. When the user terminal 20 receives the data from the server 10, the user terminal 20 causes a message (for example, a message "Can be used" as shown in the lower part of FIG. 3) indicating that there is no app code similar to the app code input by the user to be displayed on the setting screen SC2.

[0107] In the business support system 1 of Modification Example 7, when the application code is similar to other application codes, the user is notified that the application code is similar to other application codes. Thereby, since the business support system 1 can prevent an application code similar to other application codes from being set in the application, the convenience for the user is enhanced. For example, the business support system 1 can prevent a link to an unintended other application from being set in the post due to a misinput at the time of the user's post.

[0108] [6-8. Other Modification Examples] For example, two or more of Modification Examples 1 to 7 may be combined.

[0109] For example, in the embodiment and Modification Examples 1 to 7, the case where the business support system 1 sets an application code in the groupware application has been described. However, the business support system 1 may set a database code in a database other than the application. The parts described as applications in the embodiment and Modification Examples 1 to 7 can be read as any other database. For example, the business support system 1 not classified into groupware may set a database code in a database that is not an application. The business support system 1 may change or delete the database code.

[0110] For example, the functions described as being realized by the server 10 may be realized by the user terminal 20. In this case, the function may be realized by a browser script or an application installed in the user terminal 20. For example, each function may be shared by a plurality of computers or may be realized by one computer.

Description of Reference Numerals

[0111] 1 Business support system, 10 Server, 11, 21 Control unit, 12, 22 Memory unit, 13, 23 Communication unit, 20 User terminal, 24 Operation unit, 25 Display unit, 100 Data storage unit, 101 Application code acquisition unit, 102 Application code setting unit, 103 Business support unit, 104 Request reception unit, 105 Acquisition request reception unit, 106 Transmission unit, 107 Limitation unit, 108 Release unit, 109 Similar notice unit, 200 Data storage unit, 201 Display control unit, 202 Operation reception unit, B21 Button, DB1 Application database, DB2 Thread database, F20 Input form, F30 Input form, I11 Icon, L10 Record list, SC1 Application screen, SC2 Setting screen, SC3 Thread screen.

Claims

1. A database code acquisition unit that acquires a database code, which is a code for identifying a database created for business support; A database code setting unit that sets the database code in the database; A business support unit that determines whether a submission to the business support system includes the database code, and if it is determined that the submission includes the database code, sets a link to the database in the submission; A request reception unit that receives a request for changing or deleting the database code; comprising; The database code setting unit changes or deletes the database code based on the request. A business support system.

2. The database code acquisition unit acquires the database code input by the user, rather than a code automatically generated by the business support system, and different from the name of the database. The business support system according to claim 1.

3. The business support unit determines whether the submission includes a combination of the database code, a specific symbol, and information for identifying a record in the database, and if it is determined that the submission includes the combination, sets a link to the record in the database in the submission. The business support system according to claim 1 or 2.

4. The business support unit does not set a link to the database in the submission if the database code is changed or deleted after the submission, and sets a link to the database in the submission if the database code has not been changed or deleted after the submission. The business support system according to claim 1 or 2.

5. The business support unit does not set a link to another database in the submission if the database code is changed or deleted after the submission, even if the database code is set in another database, and sets a link to the other database in the submission if it is determined that a submission made after the database code is set in the other database includes the database code. The business support system according to claim 4.

6. Even if the database code is changed after the submission is made, the business support department sets a link to the database for the submission including the database code before the change. The business support system according to claim 1 or 2.

7. Even if the database code is set to another database after the database code is changed, the business support department sets a link to the database for the submission including the database code before the change. The business support system according to claim 6.

8. The business support system is an acquisition request reception unit capable of receiving an acquisition request for the database code from another business support system, a transmission unit that transmits information on a combination of the database code and a link corresponding to the database code to the other business support system when the acquisition request is received; The business support system according to claim 1 or 2, further comprising:

9. The business support system further includes a restriction unit that restricts the database code from being set to another database when the database code is changed or deleted. The business support system according to claim 1 or 2.

10. The business support system further includes a release unit that releases the restriction on the database code by the restriction unit based on a predetermined condition. The business support system according to claim 9.

11. When the database code is similar to another database code, the business support system further includes a similarity notification unit that notifies a user that the database code is similar to the other database code. The business support system according to claim 1 or 2.

12. A computer acquires a database code that is a code for identifying a database created for business support, sets the database code in the database, determines whether a submission to the business support system includes the database code, and if it is determined that the submission includes the database code, sets a link to the database for the submission, receives a request for changing or deleting the database code, changes or deletes the database code based on the request. Business support method.

13. A database code acquisition unit that acquires a database code, which is a code for identifying a database created for business support. A database code setting unit that sets the database code in the database. A business support unit that determines whether a post to the business support system includes the database code, and if it is determined that the post includes the database code, sets a link to the database in the post. A request reception unit that receives a request for changing or deleting the database code. Causing a computer to function as Based on the request, the database code setting unit changes or deletes the database code. Program.

Images