Patent Application
20220391045
This application is based on and claims priority under 35 USC 119 from Japanese Patent Application No. 2021-095569 filed Jun. 8, 2021.
The present invention relates to an information processing apparatus, a non-transitory computer readable medium storing an information processing program, and an information processing method.
In the related art, in a case of performing a task for target data on a display screen, an instruction related to the target data has been input by operating an operator displayed on the display screen. In addition, in the related art, a technology for enabling the operator displayed on the display screen to be changed has been suggested.
For example, JP2016-51427A discloses an information processing apparatus that can customize an operator displayed on a display screen and causes a user to select an operator to be displayed on the display screen from operators corresponding to a current editing mode of an application for editing target data. In addition, JP2005-284559A discloses an information processing apparatus that can switch an operator to be displayed on a display screen in accordance with an operation mode of the apparatus.
One or a plurality of users may perform the task for the target data on the display screen in a plurality of task steps. In this case, preparation of a user-associated operator associated with the users and a task step-associated operator associated with the task steps is considered.
Aspects of non-limiting embodiments of the present disclosure relate to an information processing apparatus, a non-transitory computer readable medium storing an information processing program, and an information processing method that enable a selected one of a user-associated operator or a task step-associated operator to be used in a case where one or a plurality of users perform a task for target data on a display screen in a plurality of task steps.
Aspects of certain non-limiting embodiments of the present disclosure address the above advantages and/or other advantages not described above. However, aspects of the non-limiting embodiments are not required to address the advantages described above, and aspects of the non-limiting embodiments of the present disclosure may not address advantages described above.
According to an aspect of the present disclosure, there is provided an information processing apparatus including a processor configured to select at least one of a user-associated operator that is an operator for inputting an instruction related to target data and is associated with a user, or a task step-associated operator that is an operator for inputting the instruction related to the target data and is associated with a task step related to a task performed by one or a plurality of users, based on an operator database storing the user-associated operator and the task step-associated operator and display the selected operator on a display screen.
Exemplary embodiment(s) of the present invention will be described in detail based on the following figures, wherein:
In the exemplary embodiment, the document management server 14 is a server that provides a document management service to the user. That is, in the exemplary embodiment, the information processing system 10 is a document management system that manages an electronic document as the target data. The document management service is a service for managing an electronic document transmitted from the user and providing the managed electronic document to the user in response to a request from the user. In addition, in the document management service, each user can perform an operation (editing, storage, transmission, or the like) for the managed electronic document. Specifically, the document management server 14 provides a document management application for processing the managed electronic document to the user. In a case where the document management application is executed in the user terminal 12, the above button is displayed on an execution screen of the document management application.
The information processing apparatus included in the information processing system 10 is not limited to the document management server 14. That is, the information processing system 10 is not limited to the document management system. Any apparatus that can provide the button displayed on the display screen for inputting the instruction related to the target data to the user may be used as the information processing apparatus. For example, the information processing apparatus may be a server that manages image data or music data as the target data and provides the button displayed on the display screen for inputting the instruction related to the target data to the user.
A communication interface 20 is configured to include, for example, a network adapter. The communication interface 20 performs a function of communicating with the document management server 14 via the communication line 16.
An input interface 22 is configured to include, for example, a touch panel, a button, a mouse, or a keyboard. The input interface 22 is used for inputting an instruction of the user into the user terminal 12.
A display 24 is configured to include, for example, a liquid crystal panel. Various display screens are displayed on the display 24. Particularly, the button provided from the document management server 14 and the display screen related to the document management service (both will be described in detail later) are displayed on the display 24.
A memory 26 is configured to include, for example, a hard disk drive (HDD), a solid state drive (SSD), an embedded multi media card (eMMC), a read only memory (ROM), or a random access memory (RAM). The document management application provided from the document management service (that is, the document management server 14) is installed in the memory 26.
In the embodiments above, the term “processor” refers to hardware in a broad sense. Examples of the processor include general processors (e.g., CPU: Central Processing Unit) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, and programmable logic device). In the embodiments above, the term “processor” is broad enough to encompass one processor or plural processors in collaboration which are located physically apart from each other but may work cooperatively. The order of operations of the processor is not limited to one described in the embodiments above, and may be changed.
The processor 28 controls each unit of the user terminal 12.
A communication interface 40 is configured to include, for example, a network adapter. The communication interface performs a function of communicating with the user terminal 12 via the communication line 16.
A memory 42 is configured to include, for example, an HDD, an SSD, an eMMC, a ROM, or a RAM. The memory 42 stores an information processing program for functioning of each unit of the document management server 14. In addition, the memory 42 stores the document management application provided to the user. Furthermore, as illustrated in
The user DB 44 stores information related to the user who has performed user registration for the document management service provided by the document management server 14. For example, the user DB 44 stores a user ID for uniquely identifying the user and authentication information (for example, a password) of the user in association with each other. In a case of processing the user registration, the information stored in the user DB 44 is transmitted to the document management server 14 from the user terminal 12 by the user.
The document DB 46 stores information related to the electronic document managed in the document management service. For example, the document DB 46 stores the electronic document, a document ID for uniquely identifying the electronic document, and information indicating a task space in which the electronic document is stored, in association with each other. For example, the electronic document stored in the document DB 46 is transmitted to the document management server 14 from the user terminal 12 by the user.
In the specification, the task space means a directory (or may be referred to as a folder) that is provided to the user in the document management service and is defined in the memory 42. In the memory 42, a task space structure (directory structure) used in the document management service can be defined, and the electronic document managed in the document management service can be stored at the defined task space. A task space name (directory name) or information such as a path indicating a location of the task space in the memory 42 is assigned to each task space. Accordingly, the task space can be uniquely identified.
The user can access each task space from the user terminal 12 and can perform a task for the electronic document stored in the task space. Task spaces may include a shared task space that can be accessed by a plurality of users at the same time, and in which the plurality of users perform the task in cooperation with each other. In the shared task space, the plurality of users can perform the task (document editing, document management, or the like) related to the electronic document in cooperation with each other. In addition, task spaces may include a personal task space that can be accessed by only a specific user.
A role can be defined in advance for each task space. For example, in a task space “invoice”, various invoices are stored, and a rule such that the user performs a task for each invoice by accessing the task space can be defined. In addition, for example, in a task space “first approval”, invoices transmitted from the task space “invoice” are stored, and a rule such that a first approver (for example, a department manager) performs a first approval task for each invoice by accessing the task space can be defined. Furthermore, for example, in a task space “final approval”, first-approved invoices transmitted from the task space “first approval” are stored, and a rule such that a final approver (for example, a director) performs a final approval task for each invoice by accessing the task space can be defined.
In addition, in the document management service, a series of tasks (referred to as a “workflow”) performed for one or a plurality of electronic documents in a plurality of task spaces may be able to be defined. This defined workflow is stored in the memory 42. Example of the workflow includes, as described above, a workflow including a first task step in which an invoice issuer performs the task for an electronic document “invoice” in the task space “invoice” and transmits the electronic document “invoice” to the task space “first approval”, a second task step in which the first approver performs the task for the electronic document “invoice” transmitted from the task space “invoice” and transmits the electronic document “invoice” to the task space “final approval”, and a third task step in which the final approver performs the task for the electronic document “invoice” transmitted from the task space “first approval” in the task space “final approval”. While the electronic document for which the task is performed is identical in each task step, the task for different electronic documents may be performed in each task step in the workflow.
As described above, in the exemplary embodiment, the “task step” means a step of performing the task related to a certain electronic document in a certain task space. Accordingly, in the exemplary embodiment, the “task step” is a concept including at least one of the electronic document or the task space.
The task space, the role of each task space, and the workflow may be able to be defined by the user.
The customized button DB 48 as an operator data base stores information related to a customized button. In the document management application, the user can input various instructions related to the electronic document. A plurality of buttons associated with each instruction are prepared in advance in the document management application. The user can input an intended instruction into the document management application by operating a button that is displayed on the display screen and corresponds to the instruction. Here, the customized button is a button that is customized for each user or task step, in other words, associated with the user or the task step, among buttons usable in the document management application. The customized button is a concept in contrast to a normal button that is constantly displayed on the display screen in the same manner regardless of the user and the task step (in other words, constantly displayed on the display screen in the same manner even in a case where anyone opens any electronic document in any task space in the document management application).
As illustrated in
In the embodiments above, the term “processor” refers to hardware in a broad sense. Examples of the processor include general processors (e.g., CPU: Central Processing Unit) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, and programmable logic device).
In the embodiments above, the term “processor” is broad enough to encompass one processor or plural processors in collaboration which are located physically apart from each other but may work cooperatively.
The order of operations of the processor is not limited to one described in the embodiments above, and may be changed.
The processor 54 performs functions as a document management unit 56, a display control unit 58, the registration processing unit 60, and the history management unit 62 in accordance with the information processing program stored in the memory 42.
The document management unit 56 authenticates the user who has performed the user registration in advance, by authentication processing and then, provides the document management service to the authenticated user. Specifically, the document management unit 56 executes processing related to the electronic document (for example, editing of the electronic document, storage of the electronic document in each task space, or transmission of the electronic document to the user terminal 12) in accordance with an instruction from the user.
The display control unit 58 displays the display screen related to the document management service on the display 24 of the user terminal 12 used by the user who has accessed the document management service. Specifically, in a case where the user accesses the document management service and passes authentication, the display control unit 58 displays the display screen of the document management application on the display 24 of the user terminal 12.
In addition, the display control unit 58 displays the customized button on the display 24 of the user terminal 12 together with the editing screen of the electronic document. Display control processing of the customized button by the display control unit 58 will be described later.
The registration processing unit 60 registers a user-associated registration button as a part of a user-associated operator in accordance with the instruction from the user. The user-associated registration button is a customized button that is registered by the user and is associated with the user. The user can select one or a plurality of buttons corresponding to an instruction that can be input into the document management application, and register the button as the user-associated registration button. The invention is not limited thereto. For example, the user can register a button for inputting an instruction specific to the user as the user-associated registration button. For example, the instruction specific to the user is an instruction to attach a stamp having a name of the user to the electronic document. Alternatively, the user can register a button associated with an instruction frequently input by the user as the user-associated registration button. The registration processing unit 60 stores the user ID of the user and the user-associated registration button selected by the user in the registration DB 50 in association with each other.
In addition, the registration processing unit 60 registers a document-associated registration button as a part of a target data-associated operator in accordance with the instruction from the user. The document-associated registration button is a customized button that is registered by the user and is associated with a certain electronic document stored in the document DB 46. The user can select one or a plurality of buttons corresponding to the instruction that can be input into the document management application, and register the button as the document-associated registration button. The invention is not limited thereto. For example, the user can register, as the document-associated registration button, a button associated with an instruction that is considered to be frequently input for the electronic document by a plurality of users including the user. The registration processing unit 60 stores the document ID of the electronic document and the document-associated registration button selected by the user in the registration DB 50 in association with each other.
Furthermore, the registration processing unit 60 registers a task space-associated registration button as a part of a task space-associated operator in accordance with the instruction from the user. The task space-associated registration button is a customized button that is registered by the user and is associated with a certain task space defined in the document management service. The user can select one or a plurality of buttons corresponding to the instruction that can be input into the document management application, and register the button as the task space-associated registration button. The invention is not limited thereto. For example, the user can register a button for inputting an instruction having a content corresponding to the task performed in the task space as the task space-associated registration button. For example, in a case where a workflow of transmitting the electronic document from the task space “invoice” to the task space “first approval” is defined, a button for transmission to the task space “first approval” can be registered in the task space “invoice” as the task space-associated registration button. Alternatively, the user can register, as the task space-associated registration button, a button associated with an instruction that is considered to be frequently input in the task space by the plurality of users including the user. The registration processing unit 60 stores the information (for example, the task space name or the path) for uniquely identifying the task space and the task space-associated registration button selected by the user in the registration DB 50 in association with each other.
As described above, in the exemplary embodiment, the “task step” is a concept including at least one of the electronic document or the task space. Thus, at least one of the document-associated registration button as the target data-associated operator or the task space-associated registration button as the task space-associated operator corresponds to a task step-associated operator.
As a method of registering the user-associated registration button, the document-associated registration button, and the task space-associated registration button (collectively referred to as the “registration button”), for example, the user can use a button registration window provided by the document management application. In the button registration window, an instruction content (may be referred to as a command) that can be input into the document management application can be selected, and registration of a button corresponding to the selected instruction content as any of the user-associated registration button, the document-associated registration button, and the task space-associated registration button can be selected. By selecting the instruction content and a type of button to be registered, the user can register a button corresponding to an intended instruction content as any of the user-associated registration button, the document-associated registration button, and the task space-associated registration button.
By doing so, the registration button can be registered for each user and each task step (that is, each electronic document or each task space).
The history management unit 62 registers, in the history DB 52, a use history of buttons (including the normal button and the customized button) that are used in the past in the document management service by the user. Particularly, the history management unit 62 registers the use history of buttons separately for each user and each task step (that is, each electronic document or each task space).
The history DB 52 is used as indicating a user-associated history button as a part of the user-associated operator. The user-associated history button is a customized button that is registered by the history management unit 62 and is associated with the user. For example, in the example in
In addition, the history DB 52 is used as indicating a document-associated history button as a part of the target data-associated operator. The document-associated history button is a customized button that is registered by the history management unit 62 and is associated with the electronic document. For example, in the example in
Furthermore, the history DB 52 is used as indicating a task space-associated history button as a part of the task space-associated operator. The task space-associated history button is a customized button that is registered by the history management unit 62 and is associated with the task space. For example, in the example in
As described above, in the exemplary embodiment, the “task step” is a concept including at least one of the electronic document or the task space. Thus, at least one of the document-associated history button as the target data-associated operator or the task space-associated history button as the task space-associated operator corresponds to the task step-associated operator.
All buttons registered in the history DB 52 may not necessarily be the user-associated history button, the document-associated history button, and the task space-associated history button (collectively referred to as the “history button”). For example, the user-associated history button of the user may be decided in accordance with the number of uses of a button used in the past by a specific user. A method of deciding the history button based on the history DB 52 will be described later.
In the following description, a concept including the user-associated registration button and the user-associated history button will be referred to as a user-associated button. A concept including the document-associated registration button and the document-associated history button will be referred to as a document-associated button. A concept including the task space-associated registration button and the task space-associated history button will be referred to as a task space-associated button. A relationship between titles of each customized button is summarized in
Hereinafter, details of the display control processing of the customized button by the display control unit 58 will be described with reference to
In a case where the user who logs in to the document management service operates the thumbnail T in the document management window 70 (refer to
Here, while the customized button includes various buttons as illustrated in
Specifically, the display control unit 58 specifies the user ID of the user based on login information of the user and then, refers to the registration DB 50 and selects the user-associated registration button 74 associated with the specified user ID. Here, with reference to
In the example in
In the example in
The display control unit 58 displays a pinning icon 78 near each registration button (in the example in
While the history button is decided based on the history DB 52, as described above, the method of deciding the history button based on the history DB 52 may employ several methods. Here, various methods of deciding the history button based on the history DB 52 will be described.
A first method is a method in which the display control unit 58 sets all buttons that are registered in the history DB 52 and are used in the past by the user as the user-associated history button 76.
Similarly, the display control unit 58 can set all buttons that are registered in the history DB 52 and are used in the past for the electronic document as the document-associated history button, and can set all buttons used in the past in the task space as the task space-associated history button.
A second method is a method in which based on the used time of the button registered in the history DB 52, the display control unit 58 sets a predetermined number of buttons dating back from the current point in time or a button used by the user within a predetermined time period dating back from the current point in time as the user-associated history button 76 among buttons used in the past by the user.
Similarly, the display control unit 58 can set a predetermined number of buttons dating back from the current point in time or a button used for the electronic document within a predetermined time period dating back from the current point in time as the document-associated history button among buttons used in the past for the electronic document, and set a predetermined number of buttons dating back from the current point in time or a button used in the task space within a predetermined time period dating back from the current point in time as the task space-associated history button among buttons used in the past for the task space.
A third method is a method in which the display control unit 58 decides the user-associated history button 76 based on the number of uses of the user for each button used in the past by the user. Specifically, the display control unit 58 sets a button that is used a large number of times in the past by the user as the user-associated history button 76. For example, the display control unit 58 sets a predetermined number of buttons in descending order from the button having the largest number of uses of the user in the past or a button used a predetermined number of times or more in the past by the user as the user-associated history button 76.
Similarly, the display control unit 58 can decide the document-associated history button based on the number of uses for each button used in the past for the electronic document, and decide the task space-associated history button based on the number of uses of each button used in the past in the task space.
A fourth method is a method in which the display control unit 58 sets a series of buttons that are used in order in the past by the user as the user-associated history button 76. For example, in a case where the user uses a plurality of specific buttons in the past many times in a specific order, the display control unit 58 can set the plurality of buttons as the user-associated history button 76. Specifically, the display control unit 58 analyzes use patterns of buttons of the user in the past based on the history DB 52 and sets a series of buttons included in a use pattern having the highest frequency of use (specifically, occurring a predetermined number of times or more) as the user-associated history button 76. For example, in a case where a frequency of use in order of note button→date stamp button→button for transmission to task space “first approval” in the past by a certain user is high, the note button, the date stamp button, and the button for transmission to the task space “first approval” can be set as the user-associated history button 76 of the user.
Similarly, the display control unit 58 can set a series of buttons that are used in order in the past for the electronic document as the document-associated history button, and can set a series of buttons used in order in the past in the task space as the task space-associated history button.
A fifth method is a method in which the display control unit 58 maintains a button that is immediately previously used by the user, and sets, as the user-associated history button 76, a button subsequent to the button immediately previously used by the user in order of use of a series of buttons that are obtained from the history DB 52 and are used in order in the past by the user. For example, in a case where the frequency of use in order of note button→date stamp button→button for transmission to task space “first approval” in the past by a certain user is high, and the user immediately previously uses the date stamp button, the button for transmission to the task space “first approval” can be set as the user-associated history button 76 of the user.
Similarly, the display control unit 58 can maintain a button that is immediately previously used for the electronic document, and set, as the document-associated history button, a button subsequent to the button immediately previously used for the electronic document in order of use of a series of buttons that are obtained from the history DB 52 and are used in order in the past for the electronic document. In addition, the display control unit 58 can maintain a button that is immediately previously used in the task space, and set, as the task space-associated history button, a button subsequent to the button immediately previously used in the task space in order of use of a series of buttons that are obtained from the history DB 52 and are used in order in the past in the task space.
In a case of employing the first method, the number of buttons displayed as the history button is increased, and the display screen may be complicated. In this case, a button having a high possibility of use by the user can be selected and displayed as the history button by employing the second to fifth methods. Accordingly, complication of the display screen may be suppressed. Any of the methods to be employed as the method of deciding the history button may be decided in advance by a manager or the like of the document management server 14, or may be able to be changed by the user.
In addition, the display control unit 58 may decide the user-associated history button, the document-associated history button, and the task space-associated history button in accordance with a content of an instruction associated with each customized button registered in the history DB 52.
For example, a date stamp or an approval stamp assigned to the electronic document by operating the date stamp button or the approval stamp button may include personal information (a name, a job position, and the like) of the user. In a case where the button for inputting the instruction specific to the user is displayed as the document-associated history button or the task space-associated history button, other users can input the instruction specific to the user. Accordingly, even in a case where the date stamp button or the approval stamp button is associated with the electronic document or the task space in the history DB 52, the display control unit 58 may not include, for example, the date stamp button or the approval stamp button in the document-associated history button and the task space-associated history button. In other words, for example, the button for inputting the instruction specific to the user may be included in only the user-associated history button.
In addition, for example, in a workflow of performing the task in the task space “invoice” and then, transmitting the electronic document related to the task to the task space “first approval”, the button for transmission to the task space “first approval” is meaningful in a case where the button for transmission to the task space “first approval” is displayed to the user performing the task in the task space “invoice”, and is not meaningful in a case where the button for transmission to the task space “first approval” is displayed to the user performing the task in the task space “first approval”. That is, in this case, the button for transmission to the task space “first approval” is said to be a button for inputting an instruction having a content corresponding to the task performed in the task space “invoice”. In this case, even in a case where the button for transmission to the task space “first approval” is associated with the user or the electronic document in the history DB 52, the display control unit 58 may not include, for example, the button for transmission to the task space “first approval” in the user-associated history button and the document-associated history button. In other words, for example, a button for inputting an instruction having a content corresponding to a task performed in a certain task space may be included in only the task space-associated history button. In still other words, for example, a button for inputting an instruction specific to a certain task space may be included in only the task space-associated history button.
The display control unit 58 may select the customized button to be displayed on the display screen in accordance with the instruction from the user. For example, as illustrated in
In a case where the user operates the switching button 80a in
In a case where the document-associated history button 86 (or the task space-associated history button) is displayed as the history button, for example, the display control unit 58 may display, on the display screen, information indicating a user who uses the history button in the past. For example, as illustrated in
In a case where the user operates the switching button 80b in
According to a selection method using the button switching window 92, the user can select a plurality of customized buttons to be displayed from the user-associated button, the document-associated button, and the task space-associated button. For example, the user-associated button and the document-associated button can be selected.
In a case where a plurality of buttons are displayed on the display screen from the user-associated button, the document-associated button, and the task space-associated button, the display control unit 58 may display, for example, the user-associated button, the document-associated button, and the task space-associated button on the display screen in display forms identifiable from each other. In the example in
In a case where the history button is displayed on the display screen, the registration processing unit 60 may register the history button displayed on the display screen as the registration button in accordance with an operation of the user performed on the display screen.
For example, as illustrated in
The operation of the user performed on the display screen for registering the history button as the registration button may be any operation and, for example, may be an operation of dragging and dropping the registration button to a specific region on the display screen.
For example, in the example in
Then, in a case where the user drags and drops the intended user-associated history button 76 (in the example in
For example, in a case where the user drags and drops the date stamp button as the user-associated history button 76 to the icon 90a, the registration processing unit 60 registers the date stamp button as the user-associated registration button of the user. In addition, for example, in a case where the user drags and drops the date stamp button as the user-associated history button 76 to the icon 90b, the registration processing unit 60 registers the date stamp button as the document-associated registration button of the electronic document currently displayed on the editing screen. In addition, for example, in a case where the user drags and drops the date stamp button as the user-associated history button 76 to the icon 90c, the registration processing unit 60 registers the date stamp button as the task space-associated registration button of the task space accessed by the user.
Even in a case where the document-associated history button or the task space-associated history button is displayed, in the same manner as described above, the registration processing unit 60 registers the document-associated history button or the task space-associated history button as the user-associated registration button, the document-associated registration button, or the task space-associated registration button by causing the user to drag and drop the document-associated history button or the task space-associated history button to the icon 98.
The above is a summary of the information processing system 10 according to the exemplary embodiment. Hereinafter, a flow of processing of the document management server 14 will be described in accordance with the flowchart illustrated in
In step S10, in a case where the user who logs in to the document management service operates the thumbnail T in the document management window 70 (refer to
In step S12, the display control unit 58 displays the customized button selected from the customized button DB 48 on the display screen by referring to the default display setting. Here, an assumption that the user-associated button is displayed is made.
In step S14, the display control unit 58 determines whether or not a display switching instruction for the customized button is received from the user. For example, the display control unit 58 determines whether or not the switching buttons 80 and 80′ (refer to
In step S16, the display control unit 58 determines which type of customized button to be displayed is indicated by the instruction received from the user.
In a case where the instruction to display the document-associated button is received from the user, a transition is made to step S18, and the display control unit 58 displays the document-associated button on the display screen instead of the user-associated button. In a case where the instruction to display the task space-associated button is received from the user, a transition is made to step S20, and the display control unit 58 displays the task space-associated button on the display screen instead of the user-associated button. Here, an assumption that the instruction to display the document-associated button is received from the user, and the display control unit 58 displays the document-associated button on the display screen instead of the user-associated button in step S18 is made.
In step S22, the display control unit 58 determines whether or not a display finish instruction for the editing screen of the electronic document is received from the user. In a case where the display finish instruction is not received, a return is made to step S14. In a case where the display switching instruction from the user is issued in step S14 again, and the instruction to display the user-associated button is received from the user in step S16 again, a transition is made to step S24. In step S24, the display control unit 58 displays the user-associated button again on the display screen instead of the document-associated button. Then, in a case where the display finish instruction is received in step S22, a transition is made to step S26.
In step S26, the display control unit 58 finishes the display of the editing screen of the electronic document and the customized button.
While the exemplary embodiment according to the exemplary embodiment of the invention is described above, the invention is not limited to the exemplary embodiment and can be subjected to various modifications without departing from a gist of the invention.
For example, in the exemplary embodiment, while the user DB 44, the document DB 46, and the customized button DB 48 are stored in the memory 42 of the document management server 14, these DBs may be stored in a memory of another apparatus accessible from the document management server 14.
The foregoing description of the exemplary embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obviously, many modifications and variations will be apparent to practitioners skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, thereby enabling others skilled in the art to understand the invention for various embodiments and with the various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2021-095569 | Jun 2021 | JP | national |
