Information processing device and information processing program

Abstract

To present objects that will be batch operation target candidates without users selecting the objects that will be the batch operation target candidates in advance.SOLUTION: An information processing device 10: receives the type of an object, and an operation content in which the plurality of objects belonging to the type of the object are collectively executed, from a user; and displays the object which satisfies a condition associated with the operation content, namely, a selection condition specified by using at least one of an attribute of the object relevant to the operation content, and the attribute of the user who instructs the operation content, among the objects relevant to the operation content, as a candidate object which becomes an operation target of the operation content, together with a non-candidate object estimated to be not the operation target of the operation content, on an operation screen.SELECTED DRAWING: Figure 14

Description

[Technical field]

[0001] The present invention relates to an information processing device and an information processing program. [Background technology]

[0002] Patent document 1 discloses an information processing system including a document management means for managing a plurality of documents, each of which is assigned an operation authority, a receiving means for receiving a processing request for a specified document group managed by the document management means, a storage means for storing corresponding to the document group an action content to be taken when the operation authorities assigned to documents included in the document group are different, and a control means for controlling processing of documents included in the document group based on the action content stored in the storage means when the operation authorities of documents included in the document group that are the subject of a processing request received by the receiving means are different. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2008-112279 A Summary of the Invention [Problem to be solved by the invention]

[0004] In conventional information processing devices that manage objects such as documents, when multiple objects are to be operated at once, the user first selects the objects to be operated on from within a folder or from the search results after searching using search conditions specified by the user, and then performs the desired operation.

[0005] However, in this case, the user needs to determine whether each object in the list of objects is the object to be operated on, and consider search conditions to narrow down the objects to be operated on, which can reduce work efficiency.

[0006] The present invention aims to provide an information processing device and an information processing program that can present objects that are candidates for a batch operation without the user having to pre-select the objects that are candidates for a batch operation from among multiple objects. [Means for solving the problem]

[0007] An information processing device according to a first aspect includes a processor, which receives from a user a type of object and operation content to be performed collectively on multiple objects belonging to that type, and displays on an operation screen, among objects related to the operation content, objects that satisfy a selection condition defined using at least one of an attribute of the object related to the operation content and an attribute of the user who specified the operation content, as candidate objects to be operated on by the operation content, together with non-candidate objects that are presumed not to be operated on by the operation content.

[0008] In the information processing device of the second aspect, in the information processing device of the first aspect, the processor manages objects in a hierarchical manner, distinguishes between the candidate objects and the non-candidate objects for each object lower than the object belonging to the received type, and displays the objects lower than the objects belonging to the type in a hierarchical manner on the operation screen.

[0009] In a third aspect of the information processing device, in the information processing device of the second aspect, the processor accepts attribute conditions of objects belonging to a hierarchy specified by the user, extracts objects that satisfy the attribute conditions from a plurality of objects belonging to the specified type, and rearranges the extracted objects and objects lower than the extracted objects into a hierarchy and displays them on the operation screen.

[0010] An information processing device according to a fourth aspect is an information processing device according to the second or third aspect, in which the processor rearranges the hierarchical structure of an object specified by the user on the operation screen and objects lower than the specified object, and displays them on the operation screen.

[0011] An information processing device according to a fifth aspect is the information processing device according to the fourth aspect, wherein the processor displays, on the operation screen, only a hierarchy that includes an object designated by the user.

[0012] In an information processing device according to a sixth aspect, in an information processing device according to any one of the first to fifth aspects, the processor controls so that, if the user is not an authorized user who has been given operation authority for the operation content for an object, the user is not able to select an object for which the operation authority has not been given as the candidate object on the operation screen.

[0013] An information processing device according to a seventh aspect is the information processing device according to the sixth aspect, in which the authorized users are defined for each combination of an object and the operation content.

[0014] An information processing program according to an eighth aspect is a program for causing a computer to execute a process of receiving from a user a type of object and operation content to be performed collectively on multiple objects belonging to that type, and displaying, on an operation screen, objects related to the operation content that satisfy a selection condition defined using a condition associated with the operation content, the condition being determined using at least one of an attribute of the object related to the operation content and an attribute of the user who specified the operation content, as candidate objects to be operated on by the operation content, together with non-candidate objects that are presumed not to be operated on by the operation content. Effect of the Invention

[0015] According to the first and eighth aspects, it is possible to present objects that are candidates for the batch operation without the user having to select the objects to be candidates for the batch operation from among multiple objects in advance.

[0016] According to the second aspect, there is an effect that operability can be improved compared to a case where objects are displayed on the operation screen without being organized into a hierarchy.

[0017] According to the third aspect, there is an effect that it is possible to narrow down the objects to be operated.

[0018] According to the fourth aspect, there is an effect that an object to be operated can be selected in units of a hierarchical layer.

[0019] According to the fifth aspect, there is an advantage that information relating to a specified object can be displayed in an easier-to-understand manner, as compared with a case in which all objects are displayed on the operation screen.

[0020] According to the sixth aspect, there is an effect that only authorized users can be permitted to operate objects.

[0021] According to the seventh aspect, there is an effect that the setting of the permitted user can be changed for each combination of an object and an operation content. [Brief description of the drawings]

[0022] [Figure 1] FIG. 13 is a diagram illustrating an example of a list screen. [Diagram 2] FIG. 13 is a diagram showing an example of a details screen. [Diagram 3] FIG. 13 is a diagram showing an example of a cover sheet. [Figure 4] FIG. 2 is a diagram illustrating an example of a functional configuration of an information processing device. [Diagram 5] FIG. 11 illustrates an example of a user information table. [Figure 6]FIG. 11 is a diagram illustrating an example of an operation authority table. [Figure 7] FIG. 13 illustrates an example of a case configuration information table. [Figure 8] FIG. 11 is a diagram illustrating an example of a step configuration information table. [Figure 9] FIG. 11 is a diagram illustrating an example of a document type configuration information table. [Figure 10] FIG. 11 is a diagram illustrating an example of a document configuration information table. [Figure 11] FIG. 13 is a diagram illustrating an example of a collective operation related table. [Figure 12] FIG. 11 is a diagram illustrating an example of a selection condition table. [Figure 13] FIG. 2 is a diagram illustrating an example of a configuration of a main part of an electrical system in an information processing device. [Figure 14] 13 is a flowchart showing an example of the flow of a collective operation process. [Figure 15] FIG. 13 is a diagram illustrating an example of an operation screen. [Figure 16] FIG. 13 is a diagram illustrating an example of an attribute selection dialog. [Figure 17] FIG. 13 is a diagram illustrating an example of an operation screen on which an attribute has been added. [Figure 18] FIG. 13 is a diagram illustrating an example of a filtering dialog. [Figure 19] FIG. 13 is a diagram showing an example of an operation screen after attributes are filtered based on attribute conditions set in the filtering dialog. [Figure 20] FIG. 13 is a diagram showing an example of a list screen for performing collective operations on a plurality of projects as operation targets. [Figure 21] FIG. 13 is a diagram showing an example menu of batch operations to be executed on a plurality of projects. [Figure 22] FIG. 13 illustrates an example of a selection screen. [Figure 23] FIG. 13 is a diagram showing an example of an operation screen for performing a batch operation on a plurality of projects. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] Hereinafter, the present embodiment will be described with reference to the drawings. Note that the same components and processes are given the same reference numerals throughout the drawings, and duplicated explanations will be omitted.

[0024] FIG. 1 is a diagram showing an example of a list screen 2 of business applications executed by an information processing device 10, which shows the registration status of documents created in a business process for each case based on the structure of the business process.

[0025] A business process defines the flow of processing to be executed from the start to the end of a business, the products generated in the business, and the resources required to generate the products, and is made up of a number of steps.

[0026] There are no restrictions on the type of product generated in a business, and it could be, for example, a product, but in the following, as an example, various documents created to produce a product will be described as an example of a product generated in a business.

[0027] As shown in FIG. 1, each task carried out in accordance with a business process, that is, an item, is assigned attributes that indicate the nature of the item, such as a project ID, a project name, a person in charge, and a scheduled completion date.

[0028] The project ID is an identifier for uniquely identifying the project, the project name is the name of the project, the person in charge is the person in charge of the group in charge of the project, and the scheduled completion date is the scheduled completion date of the project.

[0029] The items are further managed by steps that represent the business process. The classification of steps is set for each business, so there are no restrictions on the classification, but in the example in Figure 1, they are classified into the steps of planning, development, evaluation, and release.

[0030] Furthermore, at each step, the document type that will be generated during the execution of the step is specified. The document type represents the type of document that will be generated. In the example in Figure 1, it is specified that a "development plan" and "issue management sheet" are generated and managed in the planning step, a "basic design document," a "detailed design document," and a "review result report" in the development step, a "test plan," a "test design document," a "test review result report," a "test result report," and a "quality inspection document" in the evaluation step, and a "release preparation completion report" and "release approval document" in the release step.

[0031] When a document corresponding to the document type is created in each step, the document is stored in a specified storage area, for example, by an upload operation from a person in charge of the case, and registration of the document for the case is completed.

[0032] 1, icon 3, which shows the shape of a document in solid lines, indicates that a document corresponding to the document type has already been registered in the corresponding case, and icon 4, which shows the shape of a document in dotted lines, indicates that a document corresponding to the document type has not yet been registered in the corresponding case. In other words, the list screen 2 displays the registration status of documents associated with cases so that each case can be seen at a glance.

[0033] In this way, the types of managed objects managed based on business processes are called "object types," and the above-mentioned cases, steps, document types, and documents are examples of object types. Also, the actual managed objects managed based on business processes are called "objects." Specifically, a business is an object of a business process, each project is an object of a case, and each process that makes up a project, such as planning, development, evaluation, and release, is an object of a step. Also, a process document that specifies the document type to be created in each process, such as a development plan, is an object of a document type, and the document data (also called a "document file") of a document created as a process document is an object of a document.

[0034] As can be seen from the fact that document data is associated with process documents, process documents are associated with processes, processes are associated with projects, and projects are associated with business processes, the information processing device 10 manages objects in a hierarchical manner. Business processes are the objects at the top of the hierarchy, and projects, processes, process documents, and document data are the objects at lower levels in this order.

[0035] A user operating the list screen 2 of a business application issues an instruction via the list screen 2 to execute a predefined operation on at least one object of any type.

[0036] Therefore, on the list screen 2, detail buttons 5A-5E are displayed for displaying a detail screen 6 including detailed information about the object, and when the user selects any of the detail buttons 5A-5E with a mouse or the like, the detail screen 6 of the object corresponding to that button is displayed. The detail button 5A is a button for displaying the detail screen 6 of the project. The detail button 5B is a button for displaying the detail screen 6 of the planning process, the detail button 5C is a button for displaying the detail screen 6 of the development process, the detail button 5D is a button for displaying the detail screen 6 of the evaluation process, and the detail button 5E is a button for displaying the detail screen 6 of the release process. Hereinafter, when there is no need to distinguish between the detail buttons 5A-5E in the explanation, they will be referred to as "detail button 5".

[0037] FIG. 2 is a diagram showing an example of a details screen 6 that is displayed when a user selects a details button 5A of a project represented by a project ID "A0002."

[0038] In the example of Fig. 2, buttons for performing bulk download and bulk cover sheet creation operations are displayed for the project represented by the project ID "A0002". In addition, the attributes of the selected project are displayed on the details screen 6. There are no restrictions on the attributes that can be assigned to an object, and the details screen 6 of Fig. 2 merely shows one example of attributes that are assigned to the project represented by the project ID "A0002".

[0039] The bulk download operation is an operation for transmitting, in a single operation, at least one or more registered document data items managed by information processing device 10 among the document data items belonging to each object subordinate to a specified object (in the example of FIG. 2, the project represented by the project ID “A0002”) to a pre-specified device, so that the document data can be acquired by the specified device.

[0040] In addition, the batch cover sheet creation operation is an operation for creating a cover sheet 7 to be used when the contents of a document created on paper are digitized using a device that optically reads characters and images, such as a scanner, and the digitized contents of the document are uploaded to the information processing device 10 as document data.

[0041] 3 is a diagram showing an example of the cover sheet 7. The cover sheet 7 includes code information, such as a QR code (registered trademark), which is an encoded version of transmission information used for uploading to a business process. Since the code information is represented as an image, the code information is an example of image information.

[0042] The transmission information used for uploading includes, for example, information specifying a storage area in which the document data is to be stored, a business name specifying the business in which the document data is to be registered, a project ID specifying a project in the business, and a document type name specifying the document type in the project. The information processing device 10 stores the document data associated with the transmission information in the specified storage area according to the transmission information obtained from the code information read by the scanner, updates the registration status of the document data, and manages that the document data specified by the business name, project ID, and document type name has been registered.

[0043] The header of the coversheet 7 displays information indicating which task, which project, and which document type the coversheet 7 is to be used for registering, so a user uploading document data simply places the coversheet 7 containing the registration information for that document on the first page of the document they want to upload and then scans the document, allowing the user to complete the upload operation by simply having the scanner scan the document with the coversheet 7 placed on it.

[0044] Although the above describes an example in which the contents of a document are read by a scanner, the contents of the document may also be photographed by a camera equipped with a communication function connected to a communication line such as the Internet, and the photographed contents of the document may be converted into document data by a known character recognition method. When photographing the contents of a document with a camera, the document may be photographed as a moving image or as a still image. The generated document data is uploaded to a storage destination specified by the cover sheet 7 via the information processing device 10.

[0045] When uploading multiple documents, the user places a coversheet 7 containing the registration information of each document on the first page of each document, and then overlaps the documents and scans them with the scanner; with one scanning operation, the document data created from each document is stored in a storage area specified by the code information of the coversheet 7 placed at the top of the document, and registered in the information processing device 10. In other words, the coversheet batch operation is an example of an operation related to uploading, and an operation related to uploading is an example of an operation related to sending an object.

[0046] The designated storage area in which the document data is to be stored does not necessarily have to be a folder provided in a storage device in the information processing device 10, but may be a folder provided in a storage device in an external device other than the information processing device 10. In this case, the document data is uploaded to the external device other than the information processing device 10.

[0047] Furthermore, uploading document data does not necessarily require the cover sheet 7, and the user may upload the document data by, for example, dragging and dropping an icon representing the document data he or she wishes to upload onto the icon 4 on the list screen 2 shown in Fig. 1. The icon representing the document data is an example of image information.

[0048] Since storage area information is set for each process document of each process in a project, when document data is dragged and dropped onto the icon 4 corresponding to an unregistered process document, the information processing device 10 determines the project and document type to which the uploaded document data corresponds from the position of the icon 4, and stores the document data in the storage area set for the icon 4 to complete the upload of the document data. Note that since multiple document data may be registered in one process document, the information processing device 10 may also upload the document data when the document data is dragged and dropped onto the icon 3 corresponding to a registered process document.

[0049] Fig. 4 is a diagram showing an example of a functional configuration of the information processing device 10. As shown in Fig. 4, the information processing device 10 includes each of functional units, namely, a batch operation receiving unit 11, a control unit 12, an operation authority evaluation unit 13, a user information management unit 14, an operation authority setting unit 15, an operation target evaluation unit 16, a configuration information management unit 17, a batch operation definition unit 18, and a display unit 19.

[0050] The batch operation receiving unit 11 receives the object (starting object) notified when the user selects the details button 5 corresponding to any of the objects from the list screen 2, the operation content of the batch operation selected by the user on the details screen 6 of the starting object, and identification information (user ID) for identifying the user who instructed the batch operation.

[0051] When the control unit 12 is notified of the origin object and the operation content of the batch operation on the origin object from the batch operation receiving unit 11, the control unit 12 controls other functional units included in the information processing device 10 so that the origin object is set as the top of the object hierarchy, i.e., the origin of the objects, and the instructed batch operation is executed on objects under the origin object that satisfy the selection condition associated with the operation content of the batch operation. Note that the objects under the origin object are objects that are lower than the origin object.

[0052] The operation authority evaluation unit 13, in cooperation with the user information management unit 14 and the operation authority setting unit 15 described later, evaluates, for each object under the starting object, whether or not the user who instructed the batch operation is an authorized user who has been granted operation authority for the object.

[0053] The user information management unit 14 uses a user information table 30 to manage the user information of users who perform collective operations on objects.

[0054] Fig. 5 is a diagram showing an example of the user information table 30. As shown in Fig. 5, the user information table 30 manages user attributes such as user ID, user name, gender, department, job title, and group for each user. The user attributes managed in the user information table 30 are not limited to the attributes shown in Fig. 5, and may include other attributes required for operation.

[0055] The operation authority setting unit 15 manages the operation authorities using an operation authority table 31 .

[0056] Fig. 6 is a diagram showing an example of the operation authority table 31. As shown in Fig. 6, the operation authority table 31 includes, for example, the type of object, the type of operation, and an executable condition.

[0057] In the operation authority table 31, the executable condition column specifies the conditions for authorized users for each combination of each object represented by the object type and the operation content of each operation executed by the information processing device 10. In the example of the operation authority table in Fig. 6, the first line specifies that the authorized users for the operation of creating a QR cover sheet for a test plan are the person in charge of the planning process or users with managerial authority or higher.

[0058] The operation target evaluation unit 16 obtains configuration information of objects under the origin object for which a bulk operation is instructed from the configuration information management unit 17 described later, and evaluates, for each object under the origin object, whether or not the object is a candidate for the operation target of the instructed bulk operation based on the selection conditions defined in the bulk operation definition unit 18.

[0059] Configuration information management unit 17 manages configuration information of objects for each type of object managed by information processing device 10. The configuration information of an object is a collection of information related to the object, and includes, for example, information indicating the hierarchical relationship of the object, the attributes of the object, the state of the object, and the contents of operations that can be executed on the object.

[0060] Fig. 7 is a diagram showing an example of the project configuration information table 32A managed by the configuration information management unit 17. As shown in Fig. 7, the project configuration information table 32A includes configuration information such as a project ID, project attribute information, a step indicating a process of the project, and an operation that specifies the operation content that can be performed on the project.

[0061] Fig. 8 is a diagram showing an example of a step configuration information table 32B managed by the configuration information management unit 17. As shown in Fig. 8, the step configuration information table 32B includes configuration information such as the project ID of a project including a process, a step representing a specific process in the project, attribute information of the process, the document type of the document to be managed in the process, and an operation that specifies the operation content that can be performed on the process.

[0062] Fig. 9 is a diagram showing an example of a document type configuration information table 32C managed by the configuration information management unit 17. As shown in Fig. 9, the document type configuration information table 32C includes configuration information such as the project ID of the project to which the process document belongs, the step representing the process in which the document is managed in the project, the document type of the managed document, document attribute information, an operation that specifies the operation content that can be performed on the document, and a document name that is set as the file name of the registered document when the document is registered.

[0063] Fig. 10 is a diagram showing an example of a document configuration information table 32D managed by the configuration information management unit 17. As shown in Fig. 10, the document configuration information table 32D includes configuration information such as a project ID of a project to which a document belongs, a step indicating a process in which a document is managed in a project, a document type of a managed document, a document name in which a file name of a registered document is set, an approval status in which a result of an approval operation to confirm that a registered document is an official document is set, and an operation that specifies an operation content that can be performed on a document. Note that the document name and the approval status of a document are examples of document attributes.

[0064] In this way, the information processing device 10 manages the configuration information of the objects it manages according to a hierarchy. Note that the configuration information managed in the case configuration information table 32A, the step configuration information table 32B, the document type configuration information table 32C, and the document configuration information table 32D is not limited to the configuration information shown in Fig. 7 to Fig. 10, and may include other configuration information required for operation. For example, in the document type configuration information table 32C, the planned storage date indicating the approximate deadline for registration of a process document may be managed as attribute information.

[0065] Hereinafter, tables that manage the configuration information of each object belonging to a project, such as case configuration information table 32A, step configuration information table 32B, document type configuration information table 32C, and document configuration information table 32D, will be collectively referred to as "configuration information table 32."

[0066] The collective operation definition unit 18 defines the operation contents of the individual operations that constitute the collective operation, and also defines selection information for selecting objects that are candidates for operation targets for each type of object.

[0067] Fig. 11 is a diagram showing an example of a batch operation related table 36 managed by the batch operation definition unit 18. As shown in Fig. 11, the batch operation related table 36 includes a batch operation column in which the operation name of a batch operation executable by the information processing device 10 is set, and an individual operation column in which the operation name of an individual operation constituting the batch operation is set. In the example of the batch operation related table 36 in Fig. 11, the first line defines that a batch download operation is realized by executing a download operation for one document file for each piece of document data that is the operation target of the batch download operation. Also, the second line defines that a batch cover sheet creation operation is realized by executing a cover sheet creation operation for creating a cover sheet 7 for one piece of document data for each piece of document data that is the operation target of the batch cover sheet creation operation.

[0068] 12 is a diagram showing an example of the selection condition table 37 managed by the collective operation definition unit 18. As shown in Fig. 12, the selection condition table 37 includes, for example, a single operation column indicating the operation name of the single operation, an operation target column indicating the type of object that is the operation target of the single operation, and a selection condition column for selecting objects that are operation target candidates for each object type.

[0069] The selection condition is defined using at least one of the attributes of an object related to the operation content and the attributes of a user who has instructed the batch operation.

[0070] 13 is a diagram showing an example of the configuration of a main part of an electric system in the information processing device 10. As shown in FIG.

[0071] 4, a ROM (Read Only Memory) 22 that stores an information processing program that causes the computer 20 to function as the information processing device 10, a RAM (Random Access Memory) 23 used as a temporary work area for the CPU 21, a non-volatile memory 24, and an input / output interface (I / O) 25. The CPU 21, the ROM 22, the RAM 23, the non-volatile memory 24, and the I / O 25 are connected to each other via a bus 26.

[0072] The nonvolatile memory 24 is an example of a storage device that maintains stored data even if the power supplied to the nonvolatile memory 24 is cut off, and is, for example, a semiconductor memory, but may also be a hard disk. The nonvolatile memory 24 does not necessarily need to be built into the computer 20, and may be a portable storage medium that is detachably attached to the computer 20, such as a USB (Universal Serial Bus) memory or a memory card.

[0073] To the I / O 25, for example, a communication unit 27, an input unit 28, and a display unit 29 are connected.

[0074] The communication unit 27 is connected to a communication line and has a communication protocol for performing data communication between the communication line and an external device connected thereto.

[0075] The input unit 28 is a unit that receives instructions from a user and notifies the CPU 21, and may be, for example, a button, a touch panel, a keyboard, a mouse, etc. When instructions are given by voice, a microphone may be used as the input unit 28.

[0076] The display unit 29 is a device that outputs information processed by the CPU 21, and may be, for example, a liquid crystal display, an organic EL (Electro Luminescence) display, or a projector.

[0077] Note that the units connected to the I / O 25 of the computer 20 are not limited to the units shown in Fig. 13. For example, when the information processing device 10 is incorporated in an image forming device, an image forming unit that forms an image on a recording medium and a scanner are connected to the I / O 25. For convenience of explanation, the information processing device 10 and the image forming device are described as being installed independently and connected to each other via a communication line, but an apparatus in which the functions of the information processing device 10 are incorporated in the same housing and integrated with the information processing device 10 is also an example of the information processing device 10.

[0078] Next, the operation of the information processing device 10 will be described.

[0079] FIG. 14 is a flowchart showing an example of the flow of a batch operation process executed by the CPU 21 of the information processing device 10 when the user instructs a batch operation on the details screen 6 of the origin object selected from the list screen 2, as shown in FIG.

[0080] An information processing program that defines the collective operation process is stored in advance, for example, in the ROM 22 of the information processing device 10. The CPU 21 of the information processing device 10 reads the information processing program stored in the ROM 22 and executes the collective operation process.

[0081] In step S10, the CPU 21 refers to the collective operation relating table 36 and acquires the individual operations that make up the accepted collective operation.

[0082] In step S20, CPU 21 refers to selection condition table 37 to obtain the type of object defined as the operation target of the single operation obtained in step S10.

[0083] In step S30, CPU 21 refers to configuration information table 32 and extracts, as specific objects, all objects that are subordinate to the origin object and belong to the object type obtained in step S20.

[0084] In step S40, CPU 21 selects one of the specific objects extracted in step S30. The object selected in step S40 is referred to as a "selected object." The selected object is an example of an object related to the operation content.

[0085] In step S50, the CPU 21 acquires attributes of the user who instructed the batch operation from the user information table 30, using the user ID of the user who instructed the batch operation on the details screen 6. Note that, as the user ID of the user who instructed the batch operation, for example, the user ID input by the user in the authentication process for starting the business application executed on the information processing device 10 is used.

[0086] Furthermore, CPU 21 refers to operation authority table 31 to acquire an executable condition corresponding to the combination of the selected object and the single operation acquired in step S10. For example, if the selected object is a test plan and the operation type of the single operation is cover sheet creation, this corresponds to the combination in the first row of operation authority table 31 shown in Fig. 6, so "a person in charge of planning process or managerial authority or higher" is acquired as the executable condition.

[0087] Then, CPU 21 compares the acquired user attributes with the executable conditions to determine whether the user who instructed the collective operation is an authorized user who has the operation authority for the collective operation. If the user who instructed the collective operation is an authorized user, the process proceeds to step S60.

[0088] In step S60, the CPU 21 refers to the selection condition table 37 to acquire the selection condition associated with the operation content of the single operation acquired in step S10. For example, if the operation content of the single operation is cover sheet creation, the selection condition such as "[The 'necessity' of the document type is 'mandatory'] and [The number of documents stored in the document type = 0] and [The logged-in user is included in the person in charge of the step]" is acquired. Note that "and" in the selection condition is a regular expression representing a logical product. Also, "The necessity of the document type is mandatory" means that the document type is a document type that is required to be registered in the project, and "The number of documents stored in the document type = 0" means that no process documents corresponding to the specified document type have been registered.

[0089] The contents of the selection conditions associated with the respective operation contents are merely examples, and the selection conditions are set and modified by, for example, a user having setting authority.

[0090] In step S70, CPU 21 refers to configuration information table 32 to acquire the attributes of the selected object, and determines whether or not the selected object satisfies the selection condition acquired in step S60 by using at least one of the acquired attributes of the selected object and the user attributes acquired in step S50. If the selected object satisfies the selection condition, the process proceeds to step S80.

[0091] In this case, since the selected objects satisfy the conditions to be the operation target for the collective operation instructed by the user, in step S80, CPU 21 sets the selected objects as candidate objects to be the operation targets of the collective operation, and proceeds to step S110.

[0092] On the other hand, if it is determined in the determination process of step S50 that the user who has instructed the batch operation is not an authorized user, the process proceeds to step S90.

[0093] In this case, since the user who instructed the collective operation does not have the operation authority for the selected objects in the first place, in step S90, CPU 21 sets the selected objects as objects for which the user has no operation authority, and proceeds to step S110.

[0094] If it is determined in the determination process of step S70 that the selected object does not satisfy the selection condition, the process proceeds to step S100.

[0095] In this case, the user who instructed the collective operation has the operation authority for the selected objects, but the selected objects do not satisfy the conditions to be the operation target for the collective operation instructed by the user. Therefore, in step S100, CPU 21 sets the selected objects as non-candidate objects that are not the operation target of the collective operation, and proceeds to step S110.

[0096] In step S110, the CPU 21 determines whether or not there is an unselected object that has not yet been selected in step S40 among the specific objects extracted in step S30.

[0097] If an unselected object exists, the process proceeds to step S40, where the CPU 21 selects the unselected object from the specific objects and updates the selected object.

[0098] By repeatedly executing each process from step S40 to step S110 until it is determined in the judgment process of step S110 that there are no unselected objects, each object extracted as a specific object is classified as either a candidate object, a non-candidate object, or an object without operating authority.

[0099] On the other hand, if it is determined in the determination process of step S110 that there is no unselected object, the process proceeds to step S120.

[0100] In step S120, CPU 21 displays on display unit 29 an operation screen 8 that indicates, for each object extracted as a specific object, whether the object is a candidate object, a non-candidate object, or an object without operation authority, and terminates the collective operation processing shown in FIG. 14.

[0101] Fig. 15 is a diagram showing an example of the operation screen 8 displayed on the display unit 29 by the process of step S120 in Fig. 14. Here, as an example, a description will be given using the operation screen 8 in the case where a command to create cover sheets all at once is issued for a project with a project ID of "A0002" as shown in Fig. 2. That is, in this case, the project with a project ID of "A0002" becomes the starting object.

[0102] On the operation screen 8, all specific objects belonging to the object type defined as the operation target of the batch operation are displayed so that the hierarchical relationship of the objects can be seen. As shown in Fig. 12, since the object type that is the operation target of the batch cover sheet creation is the document type, on the operation screen 8 shown in Fig. 15, for each process of the specified project, the process documents (e.g., "Development plan") belonging to the process are displayed, and the file name of the document data (e.g., "Development plan.doc") is displayed in association with each process document.

[0103] The CPU 21 associates a check box 40 with each process document and displays it on the operation screen 8, and when the object is an object for which operation authority is not available, i.e., a process document for which operation authority is not available, the CPU 21 disables the corresponding check box 40. In Fig. 15, a shaded check box 40 indicates a disabled check box 40. Note that the CPU 21 may not only disable the check box 40, but also display supplementary information regarding the operation authority of the object, such as "(No authority)", next to a process document for which authority is not available.

[0104] Furthermore, for a process document set as a candidate object, the CPU 21 sets a check mark in the corresponding check box 40, and displays the operation screen 8 in a state in which the process document has been pre-selected as a target for batch cover sheet creation. Furthermore, for a process document set as a non-candidate object, the CPU 21 does not set a check mark in the corresponding check box 40, and displays the operation screen 8 in a state in which the process document has not been pre-selected as a target for batch cover sheet creation.

[0105] To further distinguish and display candidate objects and non-candidate objects in an easily understandable manner, the CPU 21 may not only change the setting of the check mark in the check box 40 corresponding to the candidate object and the non-candidate object, but may also change at least one of, for example, the font type, font size, font dimension, and font decoration for the representation of the candidate object and the representation of the non-candidate object on the operation screen 8.

[0106] In this way, the CPU 21 distinguishes between candidate objects and non-candidate objects for each of the objects subordinate to the starting object, and displays the objects subordinate to the starting object in a hierarchy on the operation screen 8, thereby presenting the candidate objects to be operated on in a collective operation to the user.

[0107] When the user presses Create button 8A on operation screen 8, CPU 21 transmits an instruction to generate an image of coversheet 7 to the image forming device via communication unit 27 so as to generate coversheet 7 for each object (in this case, process document) for which a check mark is set in the corresponding check box 40. On the other hand, when the user presses Cancel button 8B on operation screen 8, CPU 21 cancels the instructed batch operation (in this case, batch creation of coversheets).

[0108] If the user wishes to add an object to be the target of the bulk operation, the user simply checks the check box 40 corresponding to the object to be added, and the candidate objects to be the target of the bulk operation presented by the CPU 21 and the object added by the user are ultimately set as the objects to be the target of the bulk operation.

[0109] As already explained, objects are displayed hierarchically on the operation screen 8, so that when a check mark is set in a check box 40 corresponding to a higher-level object, a check mark is automatically set by the CPU 21 in the check boxes 40 corresponding to each of the objects below the object for which the check mark has been set. Conversely, when a check mark is removed from a check box 40 corresponding to a higher-level object, a check mark is automatically removed from the check boxes 40 corresponding to each of the objects below the object for which the check mark has been removed. This improves user operability compared to a case in which the user individually sets and deletes check marks in the check boxes 40 corresponding to objects.

[0110] On the operation screen 8, an attribute button 8C is displayed in each title field representing the type of object, such as "Step" or "Document Type," and when the user presses any of the attribute buttons 8C, the CPU 21 displays an attribute selection dialog 9 on the operation screen 8 for selecting whether to display or hide the attributes of the object for the corresponding type of object.

[0111] 16 is a diagram showing an example of the attribute selection dialog 9. In the attribute selection dialog 9, the attribute names of all objects for a specified type of object are displayed together with check boxes 40, with check marks set in advance in the check boxes 40 corresponding to the attribute names displayed on the operation screen 8.

[0112] When the user sets a check mark in the check box 40 corresponding to an attribute name that the user wants to newly display on the operation screen 8 and presses the display button 9A, the CPU 21 adds a display column for displaying an attribute corresponding to the attribute name with the check mark set to the operation screen 8. When the user removes a check mark already set in the check box 40 and presses the display button 9A, the CPU 21 deletes the display column for displaying an attribute corresponding to the attribute name with the check mark removed from the operation screen 8. When the user presses the cancel button 9B, the CPU 21 closes the attribute selection dialog 9 without changing the display on the operation screen 8.

[0113] Fig. 17 is a diagram showing an example of the operation screen 8 after a setting has been made in the attribute selection dialog 9 for a document type object, i.e., a process document, so that a planned storage date is newly displayed on the operation screen 8. As shown in Fig. 17, the operation screen 8 displays a planned storage date for each process document.

[0114] 17, a filter button 42 is displayed in a title field showing the attribute name of each object on the operation screen 8, such as "Person in Charge" or "Degree of Necessity." When the user presses the filter button 42 for any attribute, the CPU 21 displays a filtering dialog 44 on the operation screen 8 for filtering the attribute of the object (referred to as a "designated object") associated with the pressed filter button 42.

[0115] 18 is a diagram showing an example of a filtering dialog 44 that is displayed when a user presses a filter button 42 corresponding to a planned storage date, which is an attribute of a process document. All attribute conditions for filtering attributes are described in the filtering dialog 44. Each attribute condition is associated with a check box 40, and when the CPU 21 displays the filtering dialog 44, the CPU 21 displays the filtering dialog 44 with a check mark already set in the check box 40 corresponding to the attribute condition that has already been set.

[0116] When the user sets a check mark in the check box 40 corresponding to the attribute condition and presses the OK button 44A, the CPU 21 extracts objects having attribute values ​​that satisfy the attribute condition for which the check mark has been set, from among the specified objects (in this case, "process document") that belong to the hierarchical level specified by the user. As shown in Fig. 18, for example, when multiple attribute conditions such as "before today" and "this month" are set for the planned storage date, the CPU 21 extracts objects that satisfy the attribute condition defined by the logical product of the multiple set attribute conditions, specifically, process documents whose planned storage date is set before today and within the current month.

[0117] When the user presses the cancel button 44B, the CPU 21 closes the filtering dialog 44 without changing the display on the operation screen 8.

[0118] Figure 19 is a diagram showing an example of the operation screen 8 displayed after attribute conditions are set on the operation screen 8 of Figure 17 such that the "person in charge" attribute of the process is the user (also called the "logged-in user") who instructed the cover code batch operation, and the "planned storage date" attribute of the process document is "before today".

[0119] 19, the CPU 21 extracts objects that satisfy the attribute condition and objects that are subordinate to the objects that satisfy the attribute condition from among the objects of the project represented by the project ID "A0002", and then rearranges the extracted objects according to the object hierarchy and displays them on the operation screen 8. Since only the hierarchy that includes the objects that satisfy the attribute condition is displayed on the operation screen 8, the user's operability is improved compared to the case where objects to be operated on in a batch operation are selected from the operation screen 8 in which all objects subordinate to the origin object are displayed as in FIG. 17.

[0120] Note that the attribute selection dialogue 9 displays preset attribute conditions, but the user can add, change, or delete attribute conditions.

[0121] When document data is uploaded using a cover sheet created in this manner, the CPU 21 stores the document data in a specified memory area in accordance with the transmission information obtained from the code information received together with the document data, and sets the registration information of the process document specified by the business name, project ID, and document type name included in the transmission information to "registered."

[0122] Although an example of performing a collective operation with one project as the starting object has been described above, the information processing device 10 also supports a collective operation with a plurality of projects as operation targets.

[0123] FIG. 20 is a diagram showing an example of a list screen 2A for performing collective operations on a plurality of projects as operation targets.

[0124] The list screen 2A displays the registration status of process documents for each process in all projects managed by the information processing device 10, similar to the operation screen 8 shown in FIG. 1, but also includes a collective operation button 46.

[0125] When the user presses the collective operation button 46, a collective operation menu prepared in the information processing device 10 is displayed as shown in FIG.

[0126] When the user selects any operation from the menu of collective operations, a selection screen 48 for selecting the objects to be subjected to the selected collective operation is displayed, as shown in FIG.

[0127] A check box 40 is associated with each object displayed on the selection screen 48, and the user selects objects to be the targets of the collective operation by checking or unchecking the check box 40. Objects corresponding to a checked check box 40 become targets of the collective operation, and objects corresponding to an unchecked check box 40 do not become targets of the collective operation.

[0128] 22 is an example of a selection screen 48 that is displayed when the user selects to create cover sheets all at once. Since a check box 40 is associated with each project and each process document in each process, the process documents for which cover sheets 7 are to be created for multiple projects can be selected all at once. For example, if check marks are placed in the check boxes 40 corresponding to the project IDs "A0003" and "A0004", respectively, and also in the check box 40 corresponding to the basic design document, cover sheets 7 for the basic design documents for the project IDs "A0003" and "A0004" are created all at once.

[0129] Also, when it is desired to select all process documents belonging to a specific process, the process name is selected, and the subordinate process documents are selected collectively. For example, when the user selects "Development" on the selection screen 48, check marks are set in the check boxes 40 associated with each process document under the development object, that is, the basic design document, the detailed design document, and the review result report. Conversely, when the user selects a process name in which check marks are set in all the check boxes 40 associated with each subordinate process document, the check marks are cleared in the check boxes 40 associated with each subordinate process document, and the selection of the subordinate process documents is deselected.

[0130] After selecting objects to be the targets of the collective operation, the user presses the selection button 48A to confirm the selected objects.

[0131] FIG. 23 is a diagram showing an example of an operation screen 8Z that is displayed after the selection button 48A is pressed.

[0132] When the CPU 21 receives the object selected on the selection screen 48 in response to pressing of the selection button 48A and the operation content of the collective operation, it executes the collective operation processing shown in FIG. 14 and displays candidate objects and non-candidate objects distinguishably on the operation screen 8Z.

[0133] Since the operation screen 8Z displays information about objects under all projects managed by the information processing device 10, the display tends to become complicated as the number of projects and the types of objects increase. Therefore, the operation screen 8Z is provided with a check box 40A for selecting whether to display only checked rows, for example. When a check mark is set in the check box 40A, the CPU 21 rearranges only the object that the user specified by setting a check mark on the operation screen 8Z and objects lower than the specified object according to the hierarchy and displays them on the operation screen 8Z. That is, the CPU 21 displays only the hierarchy including the object specified by the user on the operation screen 8Z. Note that the information about an object refers to information associated with the object, such as the object itself and the object's attributes.

[0134] Furthermore, in the project ID column of the operation screen 8Z, a fold button 50 is displayed for each project ID, and when the user presses the fold button 50, the CPU 21 folds the display row of the project corresponding to the pressed fold button 50, and does not display information on each object included under the project corresponding to the pressed fold button 50. When the CPU 21 folds the display row of the project, it displays a display that indicates that the display row of the project is folded, for example, by changing the thickness of the frame line. When the user presses the display with the mouse or the like, the CPU 21 displays the display row of the folded project again on the operation screen 8Z.

[0135] Although the batch operation process has been described using the batch cover sheet creation operation as an example, the batch operation also includes, for example, a data batch transmission operation. The data batch transmission operation is an operation for transmitting information about objects managed by the information processing device 10 to an external device, and is an example of an operation related to uploading.

[0136] The information processing device 10 executes the batch operation process shown in Fig. 14 for an object selected by a user on the list screen 2 shown in Fig. 1 as an origin object, and selects candidate objects that satisfy the selection information associated with the data batch transmission operation from the objects under the origin object. Based on the selected candidate objects, the information processing device 10 transmits the object finally selected by the user as the operation target of the data batch transmission operation to a transmission destination predetermined for each object.

[0137] The information processing device 10 may be realized as a cloud server using cloud computing, and by setting the destination of an object to another cloud server, an operation is performed to transmit candidate objects to be operated on in a collective operation presented by the information processing device 10 to the other cloud server. That is, the collective operation process of the information processing device 10 according to the present embodiment is also applied to data transmission from cloud server to cloud server.

[0138] Furthermore, if the information processing device 10 is implemented as an on-premise server within the building of the organization that operates the information processing device 10, data transmission from the on-premise server to a cloud server is implemented.

[0139] Furthermore, the batch operation process shown in FIG. 14 may be applied to an optical device such as a camera or scanner that optically reads the contents of a document, and an object selected by a user based on candidate objects presented by the optical device may be transmitted to an information device used by an individual, such as a smartphone, a tablet computer, or a wearable device.

[0140] Although the present invention has been described above using the embodiments, the present invention is not limited to the scope described in the embodiments. Various modifications or improvements can be made to the embodiments without departing from the gist of the present invention, and the forms with such modifications or improvements are also included in the technical scope of the present invention. For example, the order of processing may be changed without departing from the gist of the present invention.

[0141] In the embodiment, the bulk operation process is realized by software as an example, but the process equivalent to the flowchart shown in Fig. 14 may be implemented in, for example, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a PLD (Programmable Logic Device) and processed by hardware. In this case, the processing speed can be increased compared to when the bulk operation process is realized by software.

[0142] In this way, the CPU 21 may be replaced with a dedicated processor specialized for specific processing, such as an ASIC, an FPGA, a PLD, a graphics processing unit (GPU), or a floating point unit (FPU).

[0143] The operation of CPU 21 in the embodiment may be realized by one CPU 11 or by a plurality of CPUs 21. Furthermore, the operation of CPU 21 in the embodiment may be realized by cooperation of CPUs 21 in computers 20 located at physically separate locations.

[0144] In the above-mentioned embodiment, the information processing program is installed in the ROM 22, but the present invention is not limited to this. The information processing program according to the present invention can also be provided in a form recorded on a computer-readable storage medium. For example, the information processing program may be provided in a form recorded on an optical disc such as a CD (Compact Disc)-ROM or a DVD (Digital Versatile Disc)-ROM. The information processing program according to the present invention may also be provided in a form recorded on a portable semiconductor memory such as a USB memory or a memory card.

[0145] Furthermore, the information processing device 10 may acquire the information processing program via the communication unit 27 from an external device connected to a communication line.

[0146] The following are notes related to this embodiment.

[0147] (((1))) A processor is provided. The processor, Selecting objects to be candidates for transmission using attributes of objects managed in a project consisting of multiple processes and attributes of a user who has instructed an operation related to the transmission of the objects; generating image information by visualizing transmission information used for transmitting the object for the object to be the transmission candidate; The generated image information is output. Information processing device.

[0148] (((2))) A processor is provided. The processor, According to transmission information obtained from image information obtained by visualizing information used for transmitting an object, the image information being generated using attributes of an object managed in a project consisting of a plurality of processes and attributes of a user who has instructed an operation related to the transmission of the object, an object that is a transmission candidate associated with the transmission information is registered as a destination object designated by the transmission information. Information processing device.

[0149] (((3))) The processor selects a plurality of objects to be the candidates for transmission, and collectively generates the image information for each of the selected objects. 13. An information processing device as set forth in claim 12, wherein said information processing device is an information processing device according to claim 11.

[0150] (((4))) The attributes of the objects managed in the project include the registration status and necessity of the project. 2. An information processing device according to claim 1, wherein the first and second information processing devices are disposed in a first and second spaced apart position.

[0151] (((5))) The processor selects, as the transmission candidate, an object that has not been registered in the project and that is required to be registered in the project, when the user is granted an operation authority for an operation related to the transmission of the object. An information processing device as described in (((4))).

[0152] (((6))) On the computer, Selecting objects to be candidates for transmission using attributes of objects managed in a project consisting of multiple processes and attributes of a user who has instructed an operation related to the transmission of the objects; generating image information by visualizing transmission information used for transmitting the object for the object to be the transmission candidate; An information processing program for executing a process for outputting the generated image information.

[0153] (((7))) On the computer, An information processing program for executing a process of registering a transmission candidate object associated with transmission information as a destination object specified in the transmission information in accordance with transmission information obtained from image information that visualizes information used to transmit an object, the image information being generated using attributes of an object managed by a project consisting of multiple processes and attributes of a user who instructed an operation related to the transmission of the object.

[0154] According to (((1))), (((2))), (((6))), and (((7))), the effect is that objects that are candidates for the batch operation can be presented without the user having to select in advance the objects that are candidates for the batch operation from among a plurality of objects.

[0155] According to (((3))), it is possible to generate a plurality of pieces of image information to be used for transmitting an object with a single operation.

[0156] According to (((4))), it is possible to generate image information of an object that has not been registered in a project but is required to be registered in a project.

[0157] According to (((5))), it is possible to prevent an instruction regarding the transmission of an object received from a user who is not granted operating authority from being executed. [Explanation of symbols]

[0158] 2 (2A) List screen, 3 (4) Icon, 5 (5A, 5B, 5C, 5D, 5E) Details button, 6 Details screen, 7 Cover sheet, 8 (8Z) Operation screen, 8A Create button, 8B (9B, 44B) Cancel button, 8C Attribute button, 9 Attribute selection dialog, 9A Display button, 10 Information processing device, 11 Batch operation reception unit, 12 Control unit, 13 Operation authority evaluation unit, 14 User information management unit, 15 Operation authority setting unit, 16 Operation target evaluation unit, 17 Configuration information management unit, 18 Batch operation definition unit, 19 Display unit, 20 Computer, 21 CPU, 22 ROM, 23 RAM, 24 Non-volatile memory, 25 I / O, 26 Bus, 27 Communication unit, 28 Input unit, 29 Display unit, 30 User information table, 31 Operation authority table, 32 Configuration information table, 32A Case composition information table, 32B Step composition information table, 32C Document type composition information table, 32D Document composition information table, 36 Bulk operation related table, 37 Selection condition table, 40 (40A) Check box, 42 Filter button, 44 Filtering dialog, 44A OK button, 46 Bulk operation button, 48 Selection screen, 48A Selection button, 50 Collapse button

Claims

1. A processor is provided. The processor, A type of object managed in a hierarchical structure and a content of an operation to be performed on a plurality of objects belonging to the type are received from a user; Among objects that are subordinate to the object belonging to the received type and that are associated with the operation content, objects that satisfy a selection condition that is associated with the operation content and is defined using at least one of an attribute of the object associated with the operation content and an attribute of the user who specified the operation content are treated as candidate objects to be operated with the operation content, and are distinguished from non-candidate objects that are presumed not to be operated with the operation content, and the objects subordinate to the object belonging to the type are displayed together in a hierarchical structure on the operation screen. Information processing device.

2. The processor accepts attribute conditions of objects belonging to a hierarchical level designated by the user; An object satisfying the attribute condition is extracted from the plurality of objects belonging to the specified type, and the extracted object and objects subordinate to the extracted object are rearranged in a hierarchy and displayed on the operation screen.

2. The information processing device according to claim 1.

3. The processor rearranges the hierarchy of the object designated by the user on the operation screen and objects subordinate to the designated object, and displays the rearranged hierarchy on the operation screen.

3. The information processing device according to claim 1.

4. The processor displays on the operation screen only a hierarchy including an object designated by the user.

4. The information processing device according to claim 3.

5. The processor controls so that, if the user is not an authorized user who is given operation authority for the operation content for an object, the user does not select an object for which the operation authority is not given as the candidate object on the operation screen. The information processing device according to any one of claims 1 to 4.

6. The authorized user is defined for each combination of the object and the operation content.

6. The information processing device according to claim 5.

7. On the computer, A type of object managed in a hierarchical structure and a content of an operation to be performed on a plurality of objects belonging to the type are received from a user; An information processing program for executing a process of classifying objects that are lower than the objects belonging to the received type and that are related to the operation content, and that satisfy a selection condition that is associated with the operation content and that is defined using at least one of an attribute of the object related to the operation content and an attribute of the user who specified the operation content, as candidate objects to be operated on the operation content, and distinguishing them from non-candidate objects that are presumed not to be operated on the operation content, and displaying the objects lower than the objects belonging to the type together on an operation screen.

Images