201246095 六、發明說明： 【發明所屬之技術領域】 [0001] 本發明涉及一種流程管理方法及系統。 [先前技術3 [0002] 為滿足企事業單位管理的需要，各種以流程方式處理事 務的應用系統如專案管理系統、電子簽核系統、請假調 休系統等開始普及。在工作中，用戶除了需要保存許多 系統的鏈結位址，記憶大量的帳號和密碼以外，為了確 保要處理的事務不被遺漏，還需要逐一登錄每一個系統 查看和處理事務。雖然目前單點登錄技術已經為用戶解 決了登錄繁瑣的問題，但進入入口系統後，用戶依然需 要逐一訪問各個子系統查看是否有待處理的事務，這將 花費大量的時間。 【發明内容】 [0003] 鑒於以上内容，有必要提供一種流程管理方法及系統， 可以整合各子系統中由用戶負責的流程，便於用戶查看 和處理。 [0004] 一種流程管理方法，包括以下步驟：建立步驟一：在運 行有若干個子系統的電腦的資料庫中建立一個子系統帳 號關聯表，該子系統帳號關聯表中記錄有該若干個子系 統的入口系統的入口帳號與子系統帳號的對應關係；建 立步驟二：在該資料庫中建立一個空白的流程表；記錄 步驟：當任一子系統中創建了新的子流程時，將該子流 程的資訊記錄在該流程表中；第一讀取步驟：當透過入 口帳號登錄入口系統時，從該子系統帳號關聯表中讀取 100116756 表單編號A0101 第4頁/共22頁 1002028160-0 201246095 权口帳號對應的各子系統㈣；第二讀取步驟：讀取 絲子系祕號在流㈣巾對應的各個子餘的資訊； 顯^驟.將該各個子流程的資訊根據絲狀態以流程 列表的形式顯示出來；鏈結步驟：根據該資料庫中保存 的各子系統的頁面鏈結位址，為該流㈣表中的各子流 程建立調用該子流程的操作頁面的鏈結；載人步驟：當 用戶在該流程列表中需要操作的子絲時，載入: 子流程的操作頁面；更新步驟：根據用戶對該子流程進 行的操作更新流程表。 剛-㈣程管理“ m域組，用於在運行有若 干個子系統的電腦的資料庫中建立—個子系統帳號關聯 表’該子系紐Μ聯表巾記錄有該若干個子系統的入 口系統的人口帳號與子系紐號的對應關係；所述建立 模組，還用於在該資料庫中建立一個空白的流程表；記 錄模組，用於當任-子系統中創建了新的子流程時將 該子流程的資訊記錄在該流程表中；第一讀取模組，用 於當透過入口帳號登錄入口系統時，從該子系統帳號關 聯表中讀取該入口帳號對應的各子系統帳號；第二讀取 模組，用於讀取該各子系統帳號在流程表中對應的各個 子流程的資訊；顯示模組，用於將該各個子流程的資訊 .根據流程狀態以流程列表的形式顯示出來；鍵結模組， 用於根據該資料庫中保存的各子系統的頁面鏈結位址， 為該流程列表中的各子流程建立調用該子流程的操作頁 面的鏈結；載入模組，用於當用戶在該流程列表中選擇 需要操作的子流程時，載入該子流程的操作頁面；更新 100116756 表單編號Α0101 第5頁/共22頁 1002028160-0 201246095 模組，用於根據用戶對該子流程進行的操作更新流程表 0 [0006] 相較於習知技術，本發明可以整合各子系統中由用戶負 責的流程，便於用戶查看和處理。 【實施方式】 [0007] 參閱圖1所示，係本發明流程管理系統較佳實施方式的運 行環境圖。在本實施方式中，流程管理系統3運行於電腦 1中。該電腦1中還運行有若干個以流程方式處理事務的 應用系統，如電子簽核系統、請假調休系統、專案管理 系統等。在每個應用系統中可以創建若干個主流程，每 個主流程對應於唯一的ID號，代表一件事務的處理流程 。每個主流程中包括若干個子流程，每個子流程對應於 唯一的ID號，表示該事務處理流程中的一個階段，且每 個子流程都有相應的負責人。所屬主流程的ID號相同的 子流程屬於同一個主流程。 [0008] 例如在請假調休系統中進行請假事務的處理流程，需要 經過創建、確認、審核、核準、完成五個階段，則在請 假調休系統中可以創建一個請假主流程，並根據各子流 程的處理進度依次在該主流程中創建流程階段為創建、 確認、審核、核準和完成的五個子流程。 [0009] 當用戶需要訪問該若干個應用系統時，可以分別登錄每 個應用系統，也可以使用單點登錄技術透過登錄入口系 統4而訪問該若干應用系統。該若干個應用系統即為該入 口系統4的子系統5。用戶可透過對應的子系統帳號分別 登錄各子系統5，也可透過對應的入口帳號登錄入口系統 100116756 表單編號A0101 第6頁/共22頁 1002028160-0 201246095 [0010] [0011] ο 4，從而訪問各子系統5。 此外，電腦〗中還包括儲存 料庫，料記錄各子系統5的頁^存112中建立有資 5對應的子系統帳號、入口系統切應的1 位=號各n統 帳號與子系統帳號的對應關係等資料。 〜口=:Γ於根據登錄人°系統4的人，，從 貝科㈣中讀取該人σ帳號對應的各子系統帳號，將該 各子系統帳號在各子系統5中對應的子流程的資訊以流程 列表的形式顯示在入口系統4的用戶介面上，並栽入需要 操作的子流程對應的子系統頁面。 [0012]201246095 VI. Description of the Invention: [Technical Field of the Invention] [0001] The present invention relates to a process management method and system. [Prior Art 3 [0002] In order to meet the needs of management of enterprises and institutions, various application systems that process transactions in a process such as a project management system, an electronic sign-off system, and a leave-of-day system have begun to spread. In the work, in addition to the need to save many system link addresses and memorize a large number of accounts and passwords, in order to ensure that the transactions to be processed are not missed, you need to log in to each system to view and process the transactions one by one. Although the current single sign-on technology has solved the cumbersome problem of login for users, after entering the portal system, users still need to access each subsystem one by one to check whether there are pending transactions, which will take a lot of time. SUMMARY OF THE INVENTION [0003] In view of the above, it is necessary to provide a process management method and system, which can integrate the processes responsible for the users in each subsystem, which is convenient for the user to view and process. [0004] A process management method includes the following steps: establishing step 1: establishing a subsystem account association table in a database of a computer running a plurality of subsystems, wherein the subsystem account association table records the plurality of subsystems Correspondence between the entry account of the portal system and the subsystem account; establishment step 2: establishing a blank flow table in the database; recording step: when a new sub-process is created in any subsystem, the sub-process The information is recorded in the flow chart; the first reading step: when logging in to the portal system through the portal account, reading 100116756 from the subsystem account association table Form No. A0101 Page 4 / Total 22 Pages 1002028160-0 201246095 Each sub-system corresponding to the port account (4); the second reading step: reading the information of each sub-remaining corresponding to the stream (4) towel of the silk system; displaying the information of each sub-process according to the state of the wire The form of the list is displayed; the link step: according to the page link address of each subsystem saved in the database, for each sub-process in the flow (4) table Calling the link of the operation page of the sub-process; manned step: when the user needs to operate the sub-filament in the process list, load: the operation page of the sub-process; update step: according to the operation of the sub-process by the user Update the process sheet. Just-(four)-process management "m-domain group for establishing a subsystem account association table in a database running a computer with several subsystems" is recorded in the entry system of the subsystems Correspondence between the population account number and the sub-system key number; the establishing module is also used to establish a blank flow table in the database; the recording module is used to create a new sub-process in the sub-system The information of the sub-process is recorded in the flow table; the first reading module is configured to read each subsystem corresponding to the import account from the subsystem account association table when logging in to the portal system through the portal account. An account; a second reading module, configured to read information of each sub-process corresponding to each subsystem account in the flow table; a display module for using the information of each sub-process. According to the process status, the process list The form is displayed; the keying module is configured to establish, according to the page link address of each subsystem stored in the database, a link to the operation page of the sub-process for each sub-process in the process list. The loading module is configured to load the operation page of the sub-process when the user selects the sub-process to be operated in the process list; update 100116756 form number Α 0101 page 5 / total 22 page 1002028160-0 201246095 module, For updating the flow table according to the operation performed by the user on the sub-process [0006] Compared with the prior art, the present invention can integrate the processes responsible for the user in each subsystem, which is convenient for the user to view and process. [Embodiment] 0007] is a schematic diagram of an operating environment of a preferred embodiment of the process management system of the present invention. In the present embodiment, the process management system 3 runs in the computer 1. The computer 1 also runs a number of processes. The application system for processing transactions, such as electronic sign-off system, leave adjustment system, project management system, etc. In each application system, several main processes can be created, each main process corresponding to a unique ID number, representing one piece The processing flow of the transaction. Each main process includes several sub-processes, each sub-process corresponding to a unique ID number, indicating a step in the transaction process Each sub-process has a corresponding person in charge. The sub-process with the same ID number of the main process belongs to the same main process. [0008] For example, in the process of taking leave, the process of the leave transaction needs to be created and confirmed. Five stages of reviewing, approving, and completing, in the leave system, a main leave process can be created, and the process stages are created in the main process according to the progress of each sub-process, creating, confirming, reviewing, approving, and The five sub-processes are completed. [0009] When the user needs to access the several application systems, each application system may be separately logged, or the plurality of application systems may be accessed through the login portal system 4 using the single sign-on technology. The application system is the subsystem 5 of the portal system 4. The user can log in to each subsystem 5 through the corresponding subsystem account, or log in to the portal system through the corresponding portal account. 100116756 Form No. A0101 Page 6 / Total 22 Page 1002028160 - 0 201246095 [0011] ο 4, thereby accessing each subsystem 5. In addition, the computer 〗 also includes a storage treasury, which records the sub-storage 112 of each subsystem 5 to establish a subsystem account corresponding to the capital 5, and the entry system categorizes the 1-digit number of the n-system account and the subsystem account. Correspondence and other information. 〜口=: Γ 根据 根据 根据 根据 根据 根据 根据 根据 ° ° 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据 根据The information is displayed in the form of a process list on the user interface of the portal system 4, and is loaded into the subsystem page corresponding to the sub-process that needs to be operated. [0012]
[0013] G 參閱圖2所示，係本發明流程管理系統較佳實施方式的功 能模組圖。流程管理系統3包括建立模組3〇1、記錄模組 302、第一讀取模組303、第二讀取模組304、顯示模組 305、鏈結模組3〇6、載入模組307和更新模組308。 建立模組301用於建立一個子系統帳號關聯表，並將該子 系統帳號關聯表存入資料庫20中。該子系統帳號關聯表 中記錄有各入口帳號與子系統帳號的對應關係。如圖3所 示，係子系統帳號關聯表的一個示例圖。入口帳號“ Li san”對應子系統a、子系統b、子系統c的子系統帳號 分別為“L000” 、“李三”、“Lisan” ，即以入口帳 號“Lisan”登錄入口系統4可訪問子系統a、子系統b和 子系統c，相當於分別以子系統帳號“L000”登錄子系統 a、以子系統帳號“李三”登錄子系統b、以子系統帳號 “Lisan”登錄子系統c從而訪問子系統a、子系統b和子 100116756 表單編號A0101 第7頁/共22頁 1002028160-0 201246095 系統C。 [0014] 建立模組301還用於建立一個空白的流程表，並將該流程 表存入資料庫20中。該流程表用於記錄所有子系統5中的 每個子流程的資訊，包括該子流程所屬主流程的ID號、 該子流程的ID號、該子流程所屬的子系統5的名稱、該子 流程負責人對應該子系統5的子系統帳號、該子流程的流 程階段，以及該子流程的開始時間和完成時間。 [0015] 記錄模組302用於當任一子系統5中創建了新的子流程時 ，將該子流程的資訊記錄在所建立的流程表中。 [0016] 如圖4所示，係流程表的一個示例圖。ID號為F1 〇 w 1的子 流程為新創建的一個子流程，該子流程所屬主流程的ID 號為A1，流程階段為“創建”，該子流程負責人對應子 系統a的子系統帳號為“L0 00” ，開始時間為 2010/11/12 。 [0017] 第一讀取模組303用於當透過入口帳號登錄入口系統4時 ，從所建立的子系統帳號關聯表中讀取該入口帳號對應 的各子系統帳號。 [0018] 第二讀取模組304用於讀取該入口帳號對應的各子系統帳 號在流程表中對應的各個子流程的資訊。 [0019] 顯示模組305用於將所讀取的該各個子流程的資訊根據流 程狀態以列表的形式在入口系統4的用戶介面上分別顯示 出來（以下簡稱為“流程列表”）。該流程狀態包括草 稿、處理中和已完成三個狀態。其中，草稿狀態指子流 程正在編輯中，並未創建完成，故所創建的子流程無開 100116756 表單編號A0101 第8頁/共22頁 1002028160-0 201246095 [0020] Ο [0021] [0022][0013] G Referring to FIG. 2, it is a functional block diagram of a preferred embodiment of the process management system of the present invention. The process management system 3 includes a setup module 3.1, a record module 302, a first read module 303, a second read module 304, a display module 305, a link module 3〇6, and a load module. 307 and update module 308. The establishing module 301 is configured to establish a subsystem account association table, and store the subsystem account association table in the database 20. The corresponding relationship between each entry account and the subsystem account is recorded in the subsystem account association table. As shown in Figure 3, an example diagram of a subsystem account association table is shown. The subsystem account of the access account "Li san" corresponding to subsystem a, subsystem b, and subsystem c are "L000", "Li San", and "Lisan" respectively, that is, the portal system "Lisan" is used to log in to the portal system 4 to access Subsystem a, subsystem b and subsystem c are equivalent to logging in to subsystem a with subsystem account "L000", logging in subsystem b with subsystem account "Li San", and logging in subsystem with subsystem account "Lisan". Thus access to subsystem a, subsystem b and sub-100116756 Form No. A0101 Page 7 of 22 Page 202028160-0 201246095 System C. [0014] The setup module 301 is also used to create a blank flow table and store the flow table in the database 20. The flow table is used to record information of each sub-process in all subsystems 5, including the ID number of the main process to which the sub-process belongs, the ID number of the sub-process, the name of the subsystem 5 to which the sub-process belongs, and the sub-process The responsible person corresponds to the subsystem account of subsystem 5, the process phase of the sub-process, and the start time and completion time of the sub-process. [0015] The recording module 302 is configured to record the information of the sub-process in the established flow table when a new sub-process is created in any of the subsystems 5. [0016] As shown in FIG. 4, it is an example diagram of a flow chart. The sub-process with ID number F1 〇w 1 is a newly created sub-process. The ID number of the main process belongs to A1, and the process stage is “create”. The sub-process owner corresponds to the subsystem account of subsystem a. The time is "L0 00" and the starting time is 2010/11/12. [0017] The first reading module 303 is configured to read, when the portal system 4 is logged in through the portal account, the subsystem accounts corresponding to the portal account from the established subsystem account association table. [0018] The second reading module 304 is configured to read information of each sub-process corresponding to each subsystem account corresponding to the entry account in the flow table. The display module 305 is configured to display the read information of the respective sub-flows in a list form on the user interface of the portal system 4 according to the process status (hereinafter referred to as a “flow list”). The process status includes draft, in progress, and completed three states. The draft status indicates that the sub-process is being edited and has not been created, so the sub-process created is not open. 100116756 Form No. A0101 Page 8 of 22 1002028160-0 201246095 [0020] [0022]
[0023] 始時間。處理中狀態指子流程有開始時間，但並未完成 ，故無完成時間。已完成狀態指子流程已完成而有完成 時間。 例如，入口帳號“Zhang”在圖3所示的子系統帳號關聯 表中對應的子系統帳號分別為“Ζ00Γ 、“張一”和“ Zhang” 。其中只有子系統帳號“Ζ00Γ和“Zhang”在 圖4所示的流程表中對應有子流程。子系統帳號“Z001” 對應的子流程的ID號為Flow2，流程狀態為正在處理中， 而子系統帳號“Zhang”對應的子流程的ID號為Flowl6 ，流程狀態為已完成。根據流程狀態顯示的處理中流程 列表如圖5所示，序號1顯示的子流程即為ID號為Flow2 的子流程。 鏈結模組306用於根據資料庫20中保存的各子系統5的頁 面鏈結位址，為流程列表中的各子流程建立調用該子流 程的操作頁面的鏈結。 載入模組307用於當用戶在流程列表中選擇需要操作的子 流程，如選擇該子流程的序號時，透過為該子流程建立 的鏈結，載入該子流程的操作頁面，供用戶訪問該操作 頁面以及對該子流程進行操作。 更新模組308用於根據用戶對該子流程進行的操作更新流 程表。例如該子流程正在處理中，用戶對該子流程處理 完成後，更新模組308將更新該子流程的完成時間。用戶 對該子流程處理完成後，若該子流程不為該主流程所需 經歷的最後一個子流程，則子系統5將自動創建下一子流 100116756 表單編號A0101 第9頁/共22頁 1002028160-0 201246095 私或由用戶創建下—個子流程，記錄模組3〇2將該下一個 子流程的資訊記錄在流程表中。 剛|閱圖6所示’係本發明流程管理方法較佳實施方式的流 程圖。 [0025] 錢入步驟阳前，建立模組3()1先建立一個子系統帳號 關聯表，並將該子系統帳號關聯表存入資料庫2〇中。該 子系統帳號關聯表巾記錄有各人σ帳號與子系統帳號的 對應關係。 [0026] 模組3G1還建立-個空白的流程表，並將該流程表存 入資料庫20中。該流程表用於記錄所有子系統5中的每個 子流程的資訊，包括該子流程所屬主流程的11}號該子 流程的ID號、該子流程所屬的子系統5的名稱、該子流程 負責人對應該子系統5的子系統帳號、該子流程的流程階 段，以及s玄子流程的開始時間和完成時間。 闺纟下述絲巾，當任-子线5巾創建了新的子流程時， 記錄模組3 0 2將該子流程的資訊記錄在所建立的流程表中 〇 [0028] 步驟S31，當透過入口帳號登錄入口系統4時，第一讀取 模組303從所建立的子系統帳號關聯表中讀取該入口帳號 對應的各子系統帳號。 [0029] 步驟S32，第二讀取模組304讀取該入口帳號對應的各子 系統帳號在流程表中對應的各個子流程的資％。 [0030] 步驟S33，顯示模組305將所讀取的該各個子流程的資訊 100116756 表單編號A0101 第10頁/共22頁 1002028160-0 201246095 [0031] [0032] Ο [0033] [0034] Ο [0035] [0036] [0037] [0038] [0039] 根據流程狀態以流程列表的形式在入口系統4的用戶介面 上分別顯示出來。該流程狀態包括草稿、處理中和已完 成三個狀態。 步驟S34，鏈結模組306根據資料庫20中保存的各子系統 5的頁面鏈結位址，為該流程列表中的各子流程建立調用 該子流程的操作頁面的鏈結。 步驟S35 ’當用戶在該流程列表中選擇需要操作的子流程 時，載入模組3〇7透過為該子流程建立的鏈結，載入該子 流程的操作頁面，供用戶訪問該操作頁面以及對該子流 程進行操作。 步驟S36 ’更新模組308根據用戶對該子流程進行的操作 更新流程表。 綜上所述，本發明符合發明專利要件，爰依法提出專利 申請。惟，以上所述者僅爲本發明之較佳實施方式，本 發明之範圍並不以上述實施方式爲限，舉凡熟悉本案技 藝之人士援依本發明之精神所作之等效修飾或變化皆 應涵蓋於以下申請專利範圍内。 【圖式簡單說明】 圖1係本發明流程管理系統較佳實施方式的運行環境圖 圖2係本發明流程管理系統較佳實施方式的功能楔組圖 圖3係子系統帳號關聯表的一個示例圖。 圖4係流程表的一個示例圖。 圖5係處理中流程列表的一個示例圖。 100116756 表單編號Α0101 第11頁/共22頁 1002028160-0 201246095 [0040] 圖6係本發明流程管理方法較佳實施方式的流程圖。 【主要元件符號說明】 [0041] 電腦 1 [0042] 儲存器2 [0043] 資料庫20 [0044] 流程管理系統3 [0045] 入口系統4 [0046] 子系統5 [0047] 建立模組301 [0048] 記錄模組302 [0049] 第一讀取模組303 [0050] 第二讀取模組304 [0051] 顯示模組30 5 [0052] 鏈結模組3 0 6 [0053] 載入模組30 7 [0054] 更新模組3 0 8 [0055] 當透過入口帳號登錄入口系統時，從子系統帳號關聯表 中讀取該入口帳號對應的各子系統帳號S31 [0056] 讀取該各子系統帳號在流程表中對應的各個子流程的資 訊S32 100116756 表單編號A0101 第12頁/共22頁 1002028160-0 201246095 [0057] [0058] [0059] [0060] Ο 將該各個子流程的資訊根據流程狀態以流程列表的形式 顯示出來S 3 3 為該流程列表中的各子流程建立調用該子流程的操作頁 面的鏈結S34 當用戶在該流程列表中選擇需要操作的子流程時，載入 該子流程的操作頁面S35 根據用戶對該子流程進行的操作更新流程表S36 ο 100116756 表單編號Α0101 第13頁/共22頁 1002028160-0[0023] Start time. The in-process status refers to the start time of the sub-process, but it is not completed, so there is no completion time. The completed status indicates that the subprocess has completed and has completed. For example, the entry account "Zhang" corresponds to the subsystem account in the subsystem account association table shown in Figure 3 as "Ζ00Γ, "Zhangyi" and "Zhang" respectively. Among them, only the subsystem accounts "Ζ00Γ and "Zhang" are in The flow table shown in FIG. 4 corresponds to a sub-flow. The ID of the sub-process corresponding to the subsystem account "Z001" is Flow2, the process status is in progress, and the sub-process ID number corresponding to the subsystem account "Zhang" is Flowl6, and the process status is completed. The process flow list displayed according to the process status is shown in Figure 5. The sub-process shown by sequence number 1 is the sub-process with ID number Flow2. The link module 306 is configured to establish, according to the page link address of each subsystem 5 stored in the database 20, a link for calling the operation page of the sub-process for each sub-flow in the process list. The loading module 307 is configured to: when the user selects a sub-process that needs to be operated in the process list, if the serial number of the sub-process is selected, the operation page of the sub-process is loaded through the link established for the sub-flow for the user Access the action page and operate on the subprocess. The update module 308 is configured to update the flow table based on operations performed by the user on the sub-flow. For example, the sub-process is being processed, and after the user completes processing of the sub-process, the update module 308 will update the completion time of the sub-process. After the user processes the sub-process, if the sub-process is not the last sub-process that the main process needs to go through, the subsystem 5 will automatically create the next sub-flow 100116756 Form No. A0101 Page 9 / Total 22 Page 1002028160- 0 201246095 Private or user-created sub-process, record module 3〇2 records the information of the next sub-process in the flow table. Just as seen in Fig. 6, a flow chart of a preferred embodiment of the flow management method of the present invention. [0025] Before the money enters the step, the module 3()1 is first established to establish a subsystem account association table, and the subsystem account association table is stored in the database. The subsystem account associated towel records the correspondence between each σ account and the subsystem account. The module 3G1 also creates a blank flow table and stores the flow table in the database 20. The flow table is used to record information of each sub-process in all subsystems 5, including the ID number of the sub-process of the main process to which the sub-process belongs, the name of the sub-system to which the sub-process belongs, and the sub-process The responsible person corresponds to the subsystem account of subsystem 5, the process phase of the sub-process, and the start time and completion time of the sap sub-process.闺纟 The following silk scarf, when the new sub-process is created, the recording module 302 records the information of the sub-process in the established flow table 〇 [0028] step S31, when When the portal system 4 is logged in through the portal account, the first reading module 303 reads the subsystem accounts corresponding to the portal account from the established subsystem account association table. [0029] Step S32, the second reading module 304 reads the capital % of each sub-process corresponding to each sub-system account corresponding to the entry account in the flow table. [0030] Step S33, the display module 305 will read the information of the respective sub-flows 100116756 Form number A0101 Page 10 / Total 22 pages 1002028160-0 201246095 [0031] [0033] [0034] Ο [0036] [0039] [0039] The flow status is displayed in the form of a flow list on the user interface of the portal system 4, respectively. The process status includes draft, in progress, and completed three states. In step S34, the link module 306 establishes a link for calling the operation page of the sub-flow for each sub-flow in the flow list according to the page link address of each subsystem 5 stored in the database 20. Step S35 'When the user selects the sub-process to be operated in the flow list, the loading module 3〇7 loads the operation page of the sub-process through the link established for the sub-flow for the user to access the operation page. And operate on the sub-process. The step S36' update module 308 updates the flow table in accordance with the operation performed by the user on the sub-flow. In summary, the present invention complies with the requirements of the invention patent and submits a patent application according to law. However, the above description is only a preferred embodiment of the present invention, and the scope of the present invention is not limited to the above-described embodiments, and equivalent modifications or variations made by those skilled in the art in light of the spirit of the present invention should be It is covered by the following patent application. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of an operating environment of a preferred embodiment of a process management system of the present invention. FIG. 2 is a functional wedge group diagram of a preferred embodiment of the flow management system of the present invention. FIG. Figure. Figure 4 is an example diagram of a flow chart. Figure 5 is an example diagram of a process list in process. 100116756 Form No. Α0101 Page 11 of 22 1002028160-0 201246095 [0040] FIG. 6 is a flow chart of a preferred embodiment of the process management method of the present invention. [Main Component Symbol Description] [0041] Computer 1 [0042] Storage 2 [0043] Database 20 [0044] Process Management System 3 [0045] Entry System 4 [0046] Subsystem 5 [0047] Module 301 is established [ 0048] recording module 302 [0049] first reading module 303 [0050] second reading module 304 [0051] display module 30 5 [0052] link module 3 0 6 [0053] loading mode Group 30 7 [0054] Update Module 3 0 8 [0055] When logging in to the portal system through the portal account, the subsystem accounts S31 corresponding to the portal account are read from the subsystem account association table [0056] Information of each sub-process corresponding to the subsystem account in the flow table S32 100116756 Form No. A0101 Page 12 / Total 22 Page 1002028160-0 201246095 [0058] [0059] [0060] 资讯 Information about each sub-process According to the process status, it is displayed in the form of a process list. S 3 3 establishes a link S34 of the operation page for calling the sub-process for each sub-process in the process list. When the user selects the sub-process to be operated in the process list, Enter the operation page of the sub-process S35 according to the user's operation on the sub-process Update flow sheet S36 ο 100116756 Form number Α0101 Page 13 of 22 1002028160-0