JP6582467B2 - Program, workflow system and processing method - Google Patents

Description

  The present invention relates to a workflow system that flexibly determines whether or not a matter can be browsed, a processing method of the workflow system, and a program.

  In the workflow system, there is a function (hereinafter referred to as tracking) that searches and browses cases that have been processed in the past. Tracking is used to check the progress and final results of projects that you are involved in, and to refer to similar projects when applying or approving them.

  In general, a trackable matter is a matter for which the user has made a decision-making process such as application / approval, and even if the user becomes unrelated to the matter due to a change, etc. Search / browse is possible.

  However, depending on the characteristics of the business to be processed on the workflow system, it may be a security risk that a user who is not currently related to the business can search and view a matter associated with the business. For example, approval documents are not processed by the user as individuals, but are applied as persons in charge of the responsible department, approval processes are also performed as persons in charge of the responsible department, and users are Not something to do.

  Nonetheless, it is not desirable in terms of security that the user can search and view the matters associated with the business even after the job is transferred from the responsible department to the outside department. In addition, if a user who has been transferred to a responsible department cannot retrieve or browse past matters associated with a business, there may be a significant inconvenience in continuing the business.

  In addition, in personnel-related work, the applicant applies only as an individual, but approval is performed by the person in charge of the department in charge, and which users should be allowed to search and view depends on the characteristics of the work. .

JP2008-299460

  In the method of Patent Document 1, an access rule is defined according to the type of form, and the access right is automatically determined according to the approved route (route) that has been circulated. If it is defined in the above access rule that a certain form is not linked to an individual, it is possible to make it impossible to view after transfer.

  However, in this method, when an organization change occurs, a case that is not associated with an individual suddenly becomes impossible to browse, and it may be inconvenient or confusing at the time of handover immediately after the organization change.

Therefore, an object of the present invention is to provide a mechanism for flexibly controlling whether or not a matter can be browsed in a workflow system .

The present invention provides an executable program in workflow system with business processes, and user department management means for managing a plurality of user-defined information with the workflow system, defining the department of the user for use in viewing permission, browsing to accept a request for browsing of projects of the business process from the user, the item state determining means projects that received the read request in the read request reception unit determines whether the processing, the item state If the project by determining means determines the processing, the user-defined information used at the time of application of the guide matter, it characterized thereby functions as control means for controlling the viewing availability of the guide matter.

According to the present invention, it is possible to provide a mechanism for flexibly controlling whether or not a matter can be browsed in a workflow system .

The figure which shows an example of a structure of the workflow system of this invention The figure which shows an example of the hardware constitutions of the information processing apparatus 101 of this invention, and the server 102 2 is a block diagram illustrating an example of a software configuration of the information processing apparatus 101 and the server 102 according to the present invention. Flow chart showing an example of browsing management reflection processing Flowchart showing an example of matter browsing permission determination processing The figure which shows an example of the table which manages the organization and user which are managed by the server 102 Diagram showing the relationship between organization and users The figure which shows an example of the table which manages the approval route, matter, and processing history which are managed by the server 102 The figure which shows an example of the table which manages the screen which sets tracking mode, and tracking mode The figure which shows an example of a browsing impossible screen

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a system configuration diagram showing an example of the configuration of a workflow system 100 of the present invention. The information processing apparatus 101 and the server 102 are connected via a network 104. The information processing apparatus 101 is a terminal such as a desktop PC, a notebook PC, a tablet PC, a smartphone, or a mobile phone. A database 103 is connected to the server 102 to supply data necessary for workflow processing. In the present invention, the server 102, the database 103, and a similar server group may have any configuration.

  Hereinafter, the hardware configuration of the information processing apparatus 101 and the server 102 illustrated in FIG. 1 will be described with reference to FIG.

  A CPU 201 controls the devices and controllers connected to the system bus 204 in an integrated manner. Further, the ROM 202 or the external memory 211 is necessary to realize a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as an OS), which is a control program of the CPU 201, or a function executed by each server or each PC. Various programs to be described later are stored.

  A RAM 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program or the like necessary for execution of processing from the ROM 202 or the external memory 211 into the RAM 203 and executing the loaded program.

  An input controller 205 controls input from a keyboard (KB) 209 or a pointing device such as a mouse (not shown). A video controller 206 controls display on a display device such as a CRT display (CRT) 210. In FIG. 2, although described as CRT 210, the display device is not limited to the CRT, but may be another display device such as a liquid crystal display. These are used by the administrator as needed.

  A memory controller 207 is an external storage device (hard disk (HD)), a flexible disk (FD), a solid state drive (SSD) for storing a boot program, various applications, font data, user files, editing files, various data, and the like. ) Or access to an external memory 211 such as a compact flash (registered trademark) memory connected to the PCMCIA card slot via an adapter.

  A communication I / F controller 208 connects and communicates with an external device via a network (for example, the LAN 400 shown in FIG. 1), and executes communication control processing in the network. For example, communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. In addition, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  Various programs to be described later for realizing the present invention are recorded in the external memory 211 and executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, definition files and various information tables used when executing the program are also stored in the external memory 211, and a detailed description thereof will be described later.

  FIG. 3 shows an example of the software configuration of the information processing apparatus 101 and the server 102 of the present invention.

  The workflow system 100 includes a case work management unit 301, an organization information management unit 302, a processing history management unit 303, a browsing availability management unit 304, a browsing availability determination unit 305, a screen output unit 306, a browsing management reflection unit 307, a reference date user department. An acquisition unit 308 is provided.

  The case work management unit 301 is a functional unit that manages case identification information and business process identification information in association with each other.

  The organization information management unit 302 is a functional unit that manages the identification information of the user and the identification information of the department to which the user belongs as association information.

  The processing history management unit 303 corresponds to the identification information of the case, the identification information of the user who has processed the case, and the identification information of the department to which the user acquired from the organization information management unit 302 performs the processing It is a functional part that is attached and managed.

  The browsing availability management unit 304 is a functional unit that manages which information managed by the processing history management unit 303 determines whether to browse a case in association with identification information of a business process corresponding to the case.

  The browsing permission / inhibition determination unit 305 is a functional unit that determines whether or not a matter can be browsed according to information for determining whether or not to browse a matter managed by the browsing availability management unit 304.

  The processing history management unit 303 is a functional unit that further manages the processing contents of the user for the case in association with each other.

  The browsing availability management unit 304 is a functional unit that manages, for each type of processing content, which information managed by the processing history management unit 303 determines whether or not to view a matter.

  The browsing permission determination unit 305 selects information corresponding to the processing contents managed by the browsing permission management unit 304 among the information managed by the processing history management unit 303 as search targets, It is a functional part that determines

  The organization information management unit 302 is a functional unit that further manages the identification information of the role to which the user belongs in association with each other.

  The processing history management unit 303 is a functional unit that further manages the identification information of the roles belonging to the user acquired from the organization information management unit 302 when the processing is performed.

  The screen output unit 306 is a functional unit that outputs a screen for inputting or changing information managed by the browsing availability management unit 304.

  The browsing management reflection unit 307 is a functional unit that reflects the input or changed information received on the screen output by the screen output unit on the browsing permission management unit 304.

  The organization information management unit 302 is a functional unit that manages the validity period in association with each other.

  The case work management unit 301 is a functional unit that further manages a reference date referring to the organization information management unit 302 in association with each other.

  The reference date user department acquisition unit 308 uses the reference date managed by the case work management unit 301 to acquire the identification information of the department to which the user who requested browsing of the case from the organization information management unit 302 belongs to the reference date. It is a functional part.

  The browsing permission / non-permission determining unit 305 includes information that includes case identification information in the processing history management unit 303 and identification information of a department to which the user who requested browsing of the case acquired by the reference date user department acquisition unit 308 belongs to the reference date. It is a functional unit that determines whether or not the item can be browsed according to whether or not is managed.

  FIG. 6 is a table relating to the organization. The “organization” in this embodiment is used as a term indicating the structure of the department, the users belonging to the department, and all of their roles.

  The department table 610 is a table representing the structure of departments constituting an organization, and stores data of “start date”, “end date”, “department ID”, and “parent department ID”. That is, the table stores past and present organization information.

  The user department table 620 is a table representing the relationship between users and departments, and stores data of “start date”, “end date”, “user ID”, “department ID”, and “role ID”. It is a table which can extract the department and role to which the user belongs in the past and the present. That is, the user department table 620 is a functional unit that shows an example of a unit that manages the identification information of a user and the identification information of the department to which the user belongs in association with organization information. The user department table 620 is a functional unit that illustrates an example of a unit that further manages the identification information of the role to which the user belongs in association with each other. Further, the user department table 620 is a functional unit that shows an example of a means for further managing effective periods in association with each other.

  The department table 610 and the user department table 620 are tables that retain history information with the “start date” as the version symbol of the department and the user department. By specifying the “start date”, the organization information and the user department of that version Information can be extracted. Also, by specifying an arbitrary date as a search condition and extracting records that are included between the “start date” and “end date”, the organization information and user department information at the arbitrary date are acquired. be able to. The department table 610 and the user department table 620 are configured to retain all the information at the time of each version, but may be configured in other forms such as retaining only the difference records that have changed from the previous version.

FIG. 7 is a diagram showing the relationship between departments and users constituting the organization shown in the department table 610 and the user department table 620 of FIG.
FIG. 8 is a table relating to the case.

  The approval route table 810 is a table for determining the “role ID” of the approver for each business process. For example, the business process with business ID = RIN01 is applied (approval route record 811), then approved by the section manager (approval route record 812), and finally approved by the general manager (approval route record 813).

  The matter table 820 indicates the “organization version” indicating when the organization approves the matter, together with the matter information such as “business ID”, “case ID”, “case name”, “draft date”, and the state of the matter. Holds “status”. In “Organization Version”, the organization version at the time of application processing is recorded, and the matter refers to the organization information of the version and determines the approver. After an organization change, it is possible to determine an approver of a case according to new organization information by updating the “organization version” of the case to a new version using a management screen (not shown) of the workflow system.

  In other words, the case table 820 is a functional unit that illustrates an example of a unit that manages case identification information and business process identification information in association with each other. The matter table 820 is a functional unit that shows an example of a management unit by further associating a reference date with reference to the user department table 620.

  In this embodiment, the item table 820 has “organization version” and the approver is determined by referring to the organization information of the “organization version”. However, the present invention is not limited to this, and the item table 820 is not limited to this. The approver may be determined by referring to the organization information at the “application date”.

  The processing history table 830 is a table that records a history of processing performed on a case such as application or approval. In the process history, the “user ID”, the “department ID”, and the “role ID” of the user who performed the process are recorded together with the process “activity” performed on the matter. Thereby, it can be understood which user has performed which role (role) in which department for the case.

  In other words, the processing history table 830 manages the identification information of the case, the identification information of the user who performed the processing on the case, and the identification information of the department to which the user belongs when the processing is performed. It is a functional part which shows an example of a means. The processing history table 830 is a functional unit that shows an example of a unit that manages the processing contents of the user with respect to the case in further association with each other. The processing history table 830 is a functional unit that shows an example of a unit that manages the identification information of the role to which the user belongs from the user department table 620 when the user performs the processing.

  In the example of the case table 820 and the processing history table 830, the case with the case ID = 001 associated with the work ID = RIN01 (planning proposal) is applied on January 10 by Andy who is a member of the department B (the case record). 821, processing history record 831), approved by section manager Daniel (processing history record 832), and status = processing (case record 821).

  Further, the case with the case ID = 002 associated with the work ID = RIN01 (planning proposal) is applied by Andy who is a member of the department B on January 10 (processing history record 833) and approved by the section manager Daniel ( Processing history record 834), finally approved by general manager Eric (processing history record 835), and status = completed (case record 822).

  Next, the browsing management reflection process in the present embodiment will be described with reference to FIG.

  In step S <b> 401, the CPU 201 of the information processing apparatus 101 requests the server 102 for a tracking mode setting screen for performing browsing management of a business process from a workflow system menu screen (not shown).

  In step S <b> 402, the CPU 201 of the server 102 receives a request for a tracking mode setting screen from the information processing apparatus 101.

  In step S403, the CPU 201 of the server 102 acquires tracking mode information. Specifically, the tracking mode of each job is acquired from the tracking mode table 910 stored in the external memory 211 of the server 102 or the external memory 211 of the database server.

  In step S404, the CPU 201 of the server 102 generates tracking mode setting screen information using the tracking mode information acquired in step S403.

  In step S405, the CPU 201 of the server 102 transmits the tracking mode setting screen information generated in step S404 to the information processing apparatus 101.

  In step S406, the CPU 201 of the information processing apparatus 101 receives tracking mode setting screen information.

  In step S407, the CPU 201 of the information processing apparatus 101 displays the tracking mode editor screen 900 (FIG. 9) on the CRT 210 using the tracking mode setting screen information received in step S406. The tracking mode editor screen 900 is an example of a screen for displaying and setting a tracking mode. On the tracking mode editor screen 900, “business ID”, “business name”, “application history tracking mode”, and “approval history tracking mode” are displayed. That is, step S407 is a step showing an example of processing for outputting a screen for inputting or changing information managed in the tracking mode table 910.

  The value of the tracking mode indicates which information in the processing history of the matter determines whether browsing is possible. Specifically, “user” or “department and role” is set as the value of the tracking mode. The tracking mode is set for each business using the tracking mode editor screen 900. The values set on the tracking mode editor screen 900 are stored in the tracking mode table 910.

  In other words, the tracking mode table 910 is an example of a unit that manages, according to which information managed in the processing history table 830, whether to view a case is determined in association with identification information of a business process corresponding to the case. It is a functional part shown. The tracking mode table 910 is a functional unit that shows an example of means for managing, for each type of processing content, which information managed in the processing history table 830 determines whether or not the item can be browsed.

  In this embodiment, the tracking mode is set using the tracking mode editor screen 900. However, the present invention is not limited to this, and information included in a setting file or the like is used as a setting value for the tracking mode. Also good.

  The application history tracking mode is “user” when the user who performed the application process can view from the history information about the matter associated with the business ID, and belongs to the department to which the user who performed the application process belongs. “Department” is set when the user can browse, and “department + role” is set when the department and role user to whom the user who performed the application process can browse.

  Similarly, the approval history tracking mode is “user” when the user who performed the approval process can view from the history information of the case linked to the business ID, and belongs to the department to which the user who performed the approval process belongs. “Department” is set when the user can browse, and “department + role” is set when the department and role user to whom the user who performed the approval process belongs can browse.

  In this embodiment, the tracking mode has two types of “application history” and “approval history”. However, the tracking mode is not limited to these two types, and is, for example, a history of processing to be saved as a draft before application. Different types such as “Save History”, “Final Approval History”, which is the approval process history of the final approver, “Rejection History”, which is the history of rejection processing by the approver, are subdivided for each activity. Or may be set.

  In step S408, the CPU 201 of the information processing apparatus 101 receives input information from the user to the tracking mode editor screen 900 displayed in step S407. Specifically, the setting change between the application history tracking mode and the approval history tracking mode on the tracking mode editor screen 900 is accepted. That is, the values of the tracking mode of the application history and the tracking mode of the approval history on the tracking mode editor screen 900 can be changed by the user.

  In this embodiment, the values that can be set in the tracking mode are “user”, “department”, “department + role”, but this is not restrictive, and a user having the same role (post) as the approver approves it. "Role" that can be viewed regardless of the department to which the person belongs, "User + Department" that enables browsing of a specific user belonging to a specific department, "User + Role" that enables browsing of a specific user of a specific role, Approver And “user + agent” or the like that can be browsed by the proxy setting person may be set.

  In step S409, the CPU 201 of the information processing apparatus 101 transmits the tracking mode input information received in step S408 to the server 102.

  In step S <b> 410, the CPU 201 of the server 102 receives the tracking mode input information transmitted from the information processing apparatus 101.

  In step S411, the CPU 201 of the server 102 reflects the tracking mode input information received in step S410 in the tracking mode information. Specifically, the tracking mode input information is reflected in the tracking mode table 910 stored in the external memory 211 of the server 102 or the external memory 211 of the database server. That is, step S411 is a step showing an example of processing for reflecting the input or changed information received on the tracking mode editor screen 900 to the tracking mode table 910.

  Next, the case browsing permission determination process in the present embodiment will be described with reference to FIG.

  In step S <b> 501, the CPU 201 of the server 102 receives a case browsing request from the information processing apparatus 101. The case browsing request includes a case ID for requesting browsing. Specifically, when an approval request mail (not shown) for a case is displayed on the CRT 210 of the information processing apparatus 101 used by the approver and a link to the case in the mail body is pressed, A browsing request for this matter is transmitted from the information processing apparatus 101 to the server 102. Note that the user ID of the user who made the case browsing request is specified using the session ID and cookie information included in the case browsing request.

  As another example, the user can use a link to the matter details screen displayed on the matter list screen (not shown) or a link to the details screen of another matter displayed on the matter details screen (not shown). When the button is pressed, the browsing request for the pressed item is transmitted from the information processing apparatus 101 to the server 102.

  In step S <b> 502, the CPU 201 of the server 102 acquires information on the browsing request item received in step S <b> 501 and stores the information in the RAM 203. Specifically, the case ID included in the browsing request is specified, and the case record is acquired from the case table 820 using the specified case ID as a search key.

  In step S503, the CPU 201 of the server 102 acquires the tracking mode of the matter acquired in step S502. Specifically, the tracking mode record is acquired from the tracking mode table 910 using the job ID of the case record acquired in step S502 as a search key.

  Steps S504 to S509 are repeated by the number of tracking modes in the tracking mode record acquired in step S503. In this embodiment, since there are two types of tracking modes, “application history” and “approval history”, first, after executing step S504 to step S509 for “application history”, next to step S504 to step for “approval history” S509 is executed.

  Note that if “Yes” is determined in Step S508 for “Application History”, or if “Yes” is determined in Step S509 for “Application History”, Steps S504 to S504 for “Approval History” are performed. Step S509 is not executed. In other words, in this embodiment, if there is history information that satisfies either of the “application history” or “approval history”, browsing of the matter is permitted, and both the “application history” and “approval history” If there is no history information to satisfy, browsing is not permitted.

  In step S504, the CPU 201 of the server 102 determines the tracking mode value of “application history” or “approval history” of the tracking mode record acquired in step S503, and the tracking mode value is “department” or “department + If it is “roll”, the process proceeds to step S505, and if it is “user”, the process proceeds to step S509.

  In step S505, the CPU 201 of the server 102 determines the status value of the matter record acquired in step S502. If the status value is “processing”, the process proceeds to step S506. If the status value is “completed”, step S507 is performed. Proceed to

  In step S <b> 506, the CPU 201 of the server 102 acquires the department and role at the time of the organization version of the case of the browsing request user from the user department table 620. Specifically, the user department table 620 is searched using the user ID of the user who made the case browsing request specified in step S501 and the organization version value of the case record acquired in step S502 as a search key. Get department and role of requesting user corresponding to organizational version of.

  That is, step S506 is an example of a process in which the user who requested browsing of the case from the user department table 620 uses the reference date managed in the case table 820 to obtain the identification information of the department belonging to the reference date. It is the step shown.

  For example, when a browsing request is received from the user ID = Andy for the case ID = 001 case (the case record 821 in FIG. 8) whose status = processing, the organization version of the case ID = 001 is the January 1st version. Therefore, the user department table 620 is searched using the user ID = Andy and the start date = 1/1 as a search key, and the department ID = B and the role ID = section member from the hit user department record 621 (FIG. 6). To get. That is, the department and role to which Andy belonged at the time of the organization version of this matter is acquired.

  In this embodiment, the department and role of the request user corresponding to the “organization version” of the matter are acquired. However, the present invention is not limited to this, and the department of the request user corresponding to the “application date” of the matter. And you may get a role. That is, when the status of the case is “processing”, browsing is permitted to the user related to the department in which the case is approved.

  As described above, because it is possible to set for each matter whether or not the matter being processed can be browsed based on the past organization information, when the organization change occurs, the matter that is not tied to the individual user becomes suddenly impossible to view. Therefore, inconvenience and confusion are not caused at the time of handover immediately after the organization change. Therefore, it is possible to eliminate the inconvenience that the viewing authority is lost due to the organization change.

  In step S507, the CPU 201 of the server 102 acquires the department and role to which the browse request user currently belongs from the user department table 620. Specifically, the user department table 620 is searched using the user ID and current date of the user who made the matter browsing request identified in step S501 as a search key, and the department to which the user who has made the matter viewing request belongs now. Get a role. In this embodiment, the search of the user department table 620 using the date as a search key means searching for a record including the current date between the start date and the end date of the user department table 620.

  As described above, since it is possible to set for each case whether or not completed cases can be viewed based on the current organization information, for cases where a user has been transferred from the department in charge of the work to the department outside the jurisdiction, the work linked to the work Can be restricted to search and browse. As a result, security risks associated with the transfer can be reduced.

  For example, when a browsing request is received for the case ID = 002 (the case record 822 in FIG. 8) with status = completed from the user ID = Andy, the user ID = Andy and the current date (here 7/10) Is used as a search key, the user department table 620 is searched, and the department ID = A and role ID = section member are acquired from the hit user department record 622 (FIG. 6). That is, the department and role to which Andy currently belongs are acquired.

  In step S508, the CPU 201 of the server 102 determines whether there is a record that matches the department (+ role) of the browsing request user in the history information of the application process or the approval process. If there is a record, the process proceeds to step S510. If the determination for “application history” has been made, the process returns to step S504 to start the determination for “approval history”. If no determination has been made for “approval history”, the process proceeds to step S511. .

  That is, step S508 is a step showing an example of a process for determining whether or not to browse a case according to information for determining whether or not to view a case managed in the tracking mode table 910. In step S508, information corresponding to the processing content managed in the tracking mode table 910 among the information managed in the tracking mode table 910 is set as a search target, and whether or not the matter can be browsed is determined. It is a step which shows an example of the process to perform. In step S508, the process history table 830 stores information on the case according to whether information including the identification information of the case and the identification information of the department to which the user who requested browsing of the case belongs is the reference date. It is a step which shows an example of the process which determines browsing permission.

  Here, when the value of the tracking mode is “department”, it is determined whether there is a record that matches the department of the viewing request user, and when the value of the tracking mode is “department + role”, Judge whether there is a record that matches department + role.

  Specifically, when the determination is made for “application history”, the case ID = the case ID specified in step S502, the activity = application, the department ID = the department ID specified in step S506 or step S507. Role ID = Searches the processing history table 830 using the role ID specified in Step S506 or Step S507 as a search key, and determines whether there is a hit record.

  For example, for the case with the case ID = 001, when the “application history” is determined, and when the department ID = B and role ID = member are acquired in step S506, the case ID = 001, activity = application The process history table 830 is searched using the department ID = B and the role ID = section as a search key to determine whether there is a hit record. In this case, the processing history record 831 is hit.

  Further, for the case with the case ID = 002, when the “application history” is determined, and the department ID = A and the role ID = member are acquired in step S506, the case ID = 002, activity = application The process history table 830 is searched using the department ID = A and the role ID = section as a search key to determine whether there is a hit record. In this case, there is no record to hit.

  In this embodiment, the match determination in step S508 is complete match. However, the present invention is not limited to this. The inclusion relationship of departments and roles (higher departments include lower departments, roles other roles) And the like may be determined.

  In step S509, the CPU 201 of the server 102 determines whether or not there is a record that matches the user ID of the viewing request user in the history information of the application process or the approval process. If there is a record, the process proceeds to step S510. ”Is returned to step S504 to start the determination for“ approval history ”, and if not so far, the process proceeds to step S511.

  Specifically, when making a determination on “application history”, the case ID = the case ID specified in step S502, the activity = application, the user ID = the case browsing request specified in step S501 was made. The processing history table 830 is searched using the user ID of the user as a search key, and the presence or absence of a hit record is determined.

  For example, for the case with the case ID = 003 (823 in FIG. 8), if the “approval history” is determined, and the user ID of the user who has made the case browsing request = Eric, the case ID = 003, The processing history table 830 is searched by using activity = approval, user ID = Eric as a search key, and the presence or absence of a hit record is determined.

  In step S510, the CPU 201 of the server 102 assumes that browsing of the case is permitted, and generates case screen information. The case screen information includes the case information acquired in step S502, the approval history information related to the case acquired from the processing history table 830, and the screen information is generated in a format such as HTML when the workflow system is a Web application. To do.

  In step S511, the CPU 201 of the server 102 assumes that browsing of the matter is not permitted, and generates browsing impossible screen information. The non-browsing screen information includes information indicating that browsing is not possible as shown in FIG.

  In step S512, the CPU 201 of the server 102 transmits the screen information generated in step S510 or step S511 to the information processing apparatus 101.

  This is the end of the description of the browsing permission determination process in FIG.

  As described above, even if there is a change, it is possible to provide a mechanism for flexibly determining whether or not to view a matter according to a business process.

  Next, a specific example of browsing permission / inhibition determination will be described with reference to FIGS.

  First, whether or not browsing is possible as of January will be described. Project 001, 002 of the planning proposal submitted by the department B member Andy has the application tracking mode = “department” (911 in FIG. 9) and the status is “processing” as of January. In the organization version (1/1 version), when browsing requests are transmitted by Andy and Bob who are department B users to whom Andy belongs, it is determined that browsing is possible (steps S504, S505, and S506 in FIG. 5). Step S508, Step S509).

  Next, since the status of projects 001 and 002 is “processing” at the time of the organization change in April, if the organization version of the project has not been changed to 1/1, browsing to Andy and Bob The state of authority continues. That is, since it is possible to browse Bob that does not belong to the department B due to the organization change in April, it is possible to carry over smoothly.

  However, for example, when the organization version of the cases 001 and 002 is changed to the 4/1 version in May, it is determined that the activity can be viewed based on the application processing history in the department information of the 4/1 edition. Andy and Chris (steps S508 and S510) who are members of the Bob, and Bob cannot be viewed (steps S508 and S511).

  Furthermore, for the case with the case ID 002, the final approval is made on 6/1 and the case status is “completed”, so that the user who can view as of June is the member of the department B in the organization information at that time. There are certain Andy and Chris (Step S504, Step S505, Step S507, Step S508, Step S509, Step S510 in FIG. 5).

  Furthermore, if the organization is changed on 7/1 and Andy and Chris are no longer members of the department B, the case 001 that has not been completed will be assigned to the department B member Andy in the organization version (4/1 version) of the matter. Chris can be browsed, and for the completed case 002, Andy and Chris who are not members of the department B are determined to be unviewable in the organization information at that time.

  If you did not change the organization version of the case that you did in May, Andy and Bob can view them until the case is completed, even if they change. The viewing authority is transferred to the user.

  Needless to say, if the application history tracking mode of the plan proposal is “user”, it is determined that the activity is viewable based on the application processing history, regardless of the status of the transfer. (Step S504, Step S509, Step S510 in FIG. 5).

  As described above, even if there is a change, it is possible to provide a mechanism for flexibly determining whether or not to view a matter according to a business process.

  In addition, since it is possible to set for each matter whether or not the matter being processed can be viewed based on past organization information, a matter that is not tied to the individual user suddenly becomes impossible to see when an organization change occurs. Thus, inconvenience and confusion are not caused at the time of handover immediately after the organization change. For this reason, it is possible to eliminate the inconvenience that the viewing authority is lost due to the organizational change.

  In addition, since it is possible to set for each case whether or not the completed case can be viewed based on the current organization information, it is possible for the user who has been transferred from the department in charge of the business to the department outside the jurisdiction to Search and browsing can be restricted. As a result, security risks associated with the transfer can be reduced.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by reading and executing.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium recording the program constitutes the present invention.

  As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  The present invention may be applied to a system constituted by a plurality of devices or an apparatus constituted by a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  The form of the program may be in the form of object code, program code executed by an interpreter, script data supplied to an OS (operating system), and the like.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

100 workflow system 101 information processing apparatus 102 server 103 database 104 network

Claims (9)

A possible program execution in the workflow system with business processes,
The workflow system,
A user department management means for managing a plurality of user definition information that defines a department to which the user belongs to be used for browsing ,
A browsing request receiving means for receiving a request for browsing the matter of the business process from the user;
A case status determination unit that determines whether a case for which a browsing request has been received by the browsing request reception unit is being processed ;
When the case status determination unit determines that the case is being processed, the program functions as a control unit that controls whether or not the case can be browsed based on user-defined information used when applying for the case . When the control means determines that the case is not being processed by the case state determination means when receiving the request for browsing the case by the browsing request receiving means, the control means The program according to claim 1, wherein browsing permission / inhibition is controlled . The program according to claim 2 , wherein the case where it is determined that the case is not being processed is a case where the case is completed . The user department management means manages the user definition information of the department to which the user belongs to be used for browsing availability by version,
The program according to any one of claims 1 to 3, wherein the control means controls whether or not the matter can be browsed based on a version of user-defined information at the time of application of the matter . 5. The program according to claim 1, wherein the user definition information used at the time of application is user definition information on an application date at the time of application of the case. The matter of the business process has a user browsing matter that can be browsed by users involved in the matter, and a department browsing matter that can be browsed only by the user of the department who applied for and approved the matter ,
It functions as a case determination means for determining whether a case for which a browsing request is received by the browsing request receiving means is a user browsing case or a department browsing case ,
The program according to any one of claims 1 to 5, wherein when the case is determined to be a department browsing case by the case determination unit, the control unit controls whether the user can view the case. When the case is determined to be a user browsing case by the case determining unit, the control unit determines whether the user can view the case depending on whether the user received by the browsing request receiving unit is related to the case. 7. The program according to claim 6, wherein the program is controlled. A workflow system with business processes,
A user department management means for managing a plurality of user definition information that defines a department to which the user belongs to be used for browsing ,
A browsing request receiving means for receiving a request for browsing the matter of the business process from the user;
A case status determination unit that determines whether a case for which a browsing request has been received by the browsing request reception unit is being processed ;
A workflow system comprising: control means for controlling whether or not to browse a case according to user-defined information used when applying for the case when the case state is determined to be being processed by the case state determination unit . A processing method in a workflow system with business processes,
The workflow system is
A user department management step for managing a plurality of user definition information that defines a department to which the user belongs to be used for browsing ;
A browsing request receiving step for receiving a request for browsing the matter of the business process from the user;
A matter status determination step for determining whether the matter for which the browse request is accepted in the browse request acceptance step is being processed ;
A processing method that executes a control step for controlling whether or not to browse the case based on the user-defined information used when applying for the case when the case state is determined to be being processed by the case state determining step; .

Images