ORIX E-Approval · Phase 2 Demo site test guide示範網站測試指南

Set up and test Phase 2 from a clean start從零開始設定並測試第二期功能

The demo site starts with user accounts and the standard case types, but no Phase 2 setup. Part 1 builds the setup as the administrator: a case type with custom fields, department heads and approval templates. Part 2 raises and approves cases with the test accounts. Part 3 covers the remaining features. Follow the parts in order. 示範網站目前只有使用者帳號和原本的案件類型,還沒有第二期的設定。第 1 部分由管理員建立設定:案件類型與自訂欄位、部門主管、審批範本;第 2 部分用測試帳號建立和審批案件;第 3 部分測其他功能。請按順序進行。

Address網址https://orix-eapproval-web.onrender.com
Password (all accounts)密碼(所有帳號)Dev@12345
Change language切換語言Avatar → Settings → Language頭像 → 設定 → 語言
Log in with the full email請用完整 email 登入 — Type alice@orix.local, not just alice. A short name is treated as a company directory login, which the demo site does not have. If the site has been idle, the first page can take up to a minute to load. 請輸入 alice@orix.local,不要只打 alice。只打名稱會被當成公司 AD 帳號登入,示範網站沒有接 AD。網站一段時間沒人使用時,第一次開啟可能要等約一分鐘。

00Test accounts測試帳號

The roles below are what each account plays after you finish Part 1.下表是完成第 1 部分設定後,各帳號在測試中的角色。

Login帳號Department部門Role in this guide在本指南中的角色
admin@orix.localOAL_TISystem admin (does all of Part 1) · Head of OAL_FAD系統管理員(負責第 1 部分)· 財務會計部主管
alice@orix.localOAL_TIInitiator (raises cases)發起人(建立案件)
bob@orix.localOAL_TIApprover in the “any one” template · team member「任一人」範本的審批人 · 團隊成員
carol@orix.localOAL_HRAHead of OAL_TI · her own department has no head科技創新部(OAL_TI)主管 · 她自己的部門沒有主管
dave@orix.localOAL_TRFixed approver in the IT template · initiator for the “any one” test · team managerIT 範本的指定審批人 ·「任一人」測試的發起人 · 團隊經理
erin@orix.localOAL_FADExtra approver for large amounts · reviewer in the “any one” template · initiator for the default template test大額案件的追加審批人 ·「任一人」範本的審閱人 · 預設範本測試的發起人

01Part 1 · Admin setup第 1 部分 · 管理員設定

Log in as登入帳號 admin@orix.local

#4a 1.1 Create the “Social Expense” case type1.1 建立「社交費用」案件類型

  1. Sidebar → Case Types → + New Case Type.側邊欄 →「案件類型」→「+ 新增案件類型」。
  2. Name (中文) 社交費用, Name (English) Social Expense. The key is generated from the English name and cannot be changed later.名稱(中文)填 社交費用,名稱(English)填 Social Expense。系統會用英文名稱產生代碼,建立後不能修改。
  3. Standard fields: tick Visible and Required for Project Sum and Currency. Leave Attachments, Target Review Completion Date and Reference Cases visible but not required.標準欄位:「金額」和「貨幣」勾選「顯示」及「必填」;「附件」、「目標審閱完成日期」、「參考案件」顯示但不必填。
  4. Click Save. Custom fields can only be added after the case type is saved.按「儲存」。案件類型要先儲存,才能加自訂欄位。
  5. + Add custom field, twice:按「+ 新增自訂欄位」,加兩個:
Label (中文 / English)名稱(中文/English)Type類型Required必填Options (中文 / English)選項(中文/English)
費用類別 / Expense CategoryDropdown下拉選單Yes是餐飲 / Meals · 禮品 / Gifts · 娛樂 / Entertainment
人數 / Number of GuestsNumber數字Yes是—

Expected: the list shows Social Expense as Active with 2 custom fields.預期:列表顯示「社交費用」為啟用,有 2 個自訂欄位。

#4b 1.2 Set department heads1.2 設定部門主管

  1. Sidebar → Department Heads. All 14 departments are listed.側邊欄 →「部門主管」,列出全部 14 個部門。
  2. OAL_TI → Carol Lee. A head does not have to belong to the department.OAL_TI → 選 Carol Lee。主管不一定要是該部門的人。
  3. OAL_FAD → System Admin.OAL_FAD → 選 System Admin。
  4. Leave every other department, including OAL_HRA and OAL_TR, unassigned. Part 2 uses OAL_HRA to test a department with no head.其他部門(包括 OAL_HRA、OAL_TR)保持未指派。第 2 部分會用 OAL_HRA 測試「部門沒有主管」。

#4c 1.3 Create three approval templates1.3 建立三個審批範本

Sidebar → Approval Templates → + New template, once for each table below. Each case type can have one active default template and one active template per department.側邊欄 →「審批範本」→「+ 新增範本」,依下面三個表格各建一個。每個案件類型可以有一個啟用中的預設範本,以及每個部門各一個啟用中的範本。

Settings the three templates share: Case type Social Expense, Workflow type Review + approval, Initiator can change approvers Locked, When the department has no head Block and ask to contact the administrator, Status Active.三個範本共同的設定:案件類型選「社交費用」,流程類型選「審閱 + 審批」,發起人能否修改審批人選「鎖住」,部門沒有主管時選「擋下,請聯絡管理員」,狀態為「啟用」。

A · Default template預設範本

Name (中文 / English)名稱(中文/English)社交費用 - 預設 / Social Expense - Default
Department部門All (default)全部(預設)
Review stage審閱階段Dynamic: initiator’s department head動態:發起人的部門主管
Approval stage 1審批第 1 階段Dynamic: initiator’s department head動態:發起人的部門主管

B · IT department templateIT 部門範本

Name (中文 / English)名稱(中文/English)社交費用 - IT / Social Expense - IT
Department部門OAL_TI
Review stage審閱階段Dynamic: initiator’s department head動態:發起人的部門主管
Approval stage 1審批第 1 階段Dynamic: initiator’s department head動態:發起人的部門主管
Approval stage 2審批第 2 階段Specific people: Dave Ho指定的人:Dave Ho
Conditional rule條件規則If Amount greater than 50000, add an approval stage: Specific people: Erin Lam如果「金額」大於 50000,就加一個審批階段:指定的人 Erin Lam

C · Treasury “any one” template庫務部「任一人」範本

Name (中文 / English)名稱(中文/English)社交費用 - 庫務 / Social Expense - Treasury
Department部門OAL_TR
Review stage審閱階段Specific people: Erin Lam指定的人:Erin Lam
Approval stage 1審批第 1 階段Specific people: Bob Wong and Carol Lee · Any one approves指定的人:Bob Wong、Carol Lee ·「任何一人批即可」

Expected: filtering the list by Social Expense shows three active templates.預期:用「社交費用」篩選,列表顯示三個啟用中的範本。

#6 1.4 Optional: a team for “My Team”1.4 選做:建立「我的團隊」用的團隊

Only needed to test the My Team list in Part 3. The team manager list shows users who hold a role named exactly manager, and My Team appears for users whose role has the permission read on TeamCase.只有要測第 3 部分的「我的團隊」才需要。團隊經理只能從擁有名為 manager 角色的使用者中選;擁有 TeamCase 的 read 權限的角色,才會看到「我的團隊」。

  1. RBAC Management → create permission: Resource TeamCase, Action read.「RBAC 管理」→ 新增權限:資源 TeamCase,動作 read。
  2. Create role: Name manager, scope User. Give it the read TeamCase permission.新增角色:名稱 manager,範圍選使用者(User);把 read TeamCase 權限加給它。
  3. User Management → Dave Ho → roles (shield icon) → add manager.「使用者管理」→ Dave Ho → 角色(盾牌圖示)→ 加上 manager。
  4. Team Management → create a team (for example “Treasury Team”), manager Dave Ho → add members Alice Chan and Bob Wong.「團隊管理」→ 新增團隊(例如「庫務團隊」),經理選 Dave Ho → 加入成員 Alice Chan、Bob Wong。

02Part 2 · Raise and approve cases第 2 部分 · 建立與審批案件

#4c #8 2.1 The IT template fills in the approvers2.1 IT 範本自動帶出審批人

Log in as登入帳號 alice@orix.local

  1. Create New Case → Case Type Social Expense. The form shows template “Social Expense - IT” and a locked flow: Review Carol · Approval 1 Carol · Approval 2 Dave.「建立新案件」→ 案件類型選「社交費用」。表單顯示範本「社交費用 - IT」及鎖住的流程:審閱 carol · 審批 1 carol · 審批 2 dave。
  2. Enter Amount 8,500: no extra stage. Change it to 120,000.金額填 8,500:沒有追加階段。改成 120,000。 Expected: an Approval 3 stage for Erin appears.預期:出現 erin 的審批第 3 階段。
  3. Fill Expense Category and Number of Guests. In Case Content, try a table, font size and colour.填「費用類別」和「人數」;案件內容試試表格、字體大小、顏色。
  4. Attach a PDF, a Word and an Excel file for the preview test in Part 3.附上 PDF、Word、Excel 各一個,供第 3 部分測預覽。
  5. Save as Draft, open the draft from Draft, then Submit.先「存為草稿」,再從「草稿」打開並送出。

#2 2.2 Review and approve2.2 審閱與審批

  1. Log in as carol@orix.local → For My Review → open Alice’s case → Mark as Reviewed.以 carol@orix.local 登入 →「待我審閱」→ 打開 alice 的案件 → 按「已審閱」。
  2. Log in as alice@orix.local → open the case → click Move to Approval.以 alice@orix.local 登入 → 打開案件 → 按「移至審批」。
  3. Approve in order: carol (stage 1) → dave (stage 2) → erin (stage 3), each from For My Approval.依序在「待我審批」批准:carol(第 1 階段)→ dave(第 2 階段)→ erin(第 3 階段)。
  4. As Carol, open Completed → Reviewed and Completed → Approved at the bottom of the sidebar.以 carol 查看側邊欄最下方「已處理 → 已審閱」及「已處理 → 已審批」。 Expected: the case is listed in both.預期:兩個資料夾都有這個案件。

#4c 2.3 Department with no head2.3 部門沒有主管

Log in as登入帳號 carol@orix.local (OAL_HRA has no head and no department template)(OAL_HRA 沒有主管,也沒有部門範本)

Start a Social Expense case.新建「社交費用」案件。 Expected: the Default template applies and shows “Your department has no department head configured”; the case cannot be submitted.預期:套用預設範本,顯示「你的部門尚未設定部門主管」,無法送出。

#4c 2.4 Default template2.4 預設範本

Log in as登入帳號 erin@orix.local (OAL_FAD has no department template)(OAL_FAD 沒有部門專用範本)

Start a Social Expense case.新建「社交費用」案件。 Expected: “Social Expense - Default” applies, with System Admin (head of OAL_FAD) as reviewer and approver.預期:套用「社交費用 - 預設」,審閱人和審批人都是 System Admin(OAL_FAD 主管)。

#4c 2.5 Any one approver is enough2.5 任何一人批即可

Log in as登入帳號 dave@orix.local (OAL_TR uses the Treasury template)(OAL_TR 套用庫務部範本)

  1. Raise and submit a Social Expense case. Erin reviews it, then Dave clicks Move to Approval.建立並送出「社交費用」案件;erin 審閱後,dave 按「移至審批」。
  2. Log in as bob@orix.local and approve.以 bob@orix.local 登入並批准。 Expected: the case is approved; Carol shows “Not required” and the case leaves her For My Approval list.預期:案件完成審批;carol 顯示「無需審批」,案件從她的「待我審批」消失。

#4c 2.6 Locked approvers2.6 鎖住審批人

After submitting, the initiator opens the case and clicks Edit.送出後,發起人打開案件按「編輯」。 Expected: only CC can be changed; reviewers and approvers are fixed by the template.預期:只能修改副本收件人,審閱人和審批人由範本決定。

To see the opposite, edit the Default template, set “Initiator can change approvers” to Can change, and start a case as Erin: the reviewer and approvers can then be edited.想看相反情況:把預設範本的「發起人能否修改審批人」改成「可以修改」,再以 erin 建案,就能修改審閱人和審批人。

03Part 3 · Other features第 3 部分 · 其他功能

#Feature功能How to test測試方法
#1End review結束審閱As Alice, raise a case with two reviewers (for example a Memo with Bob and Carol). After one reviews, Alice opens the case → End review → enters a reason. The other reviewer shows “Not reviewed”. Nothing completes automatically on the target date.以 alice 建一個有兩位審閱人的案件(例如「備忘錄」,審閱人 bob、carol)。一人審閱後,alice 打開案件 →「結束審閱」→ 填原因;另一人顯示「未審閱」。到了目標日期也不會自動完成。
#3Attachment preview附件預覽Open the case from 2.1 and click each attachment. PDF, Word (.docx), Excel, PowerPoint (.pptx), images and text files open in a window without downloading.打開 2.1 的案件,逐一點附件。PDF、Word(.docx)、Excel、PowerPoint(.pptx)、圖片及文字檔都直接在視窗中預覽,不用下載。
#5Email reminderEmail 提醒As the initiator of a case in review or approval → Remind → tick the pending people → tick Email → Send.發起人打開審閱中或審批中的案件 →「提醒」→ 勾選待處理的人 → 勾「Email」→ 送出。
#6Search and export搜尋與匯出Inbox → Advanced Filters (initiator, approver, reviewer) → change page: the filter still applies → Export Excel. Open a case and press Back: the filters are kept.收件箱 →「進階篩選」(發起人、審批人、審閱人)→ 換頁後篩選仍有效 →「匯出 Excel」。打開案件再按「返回」,篩選仍在。
#6My Team我的團隊Needs step 1.4. Log in as Dave → My Team: Alice’s and Bob’s cases are listed; filter by several priorities and departments.需先完成 1.4。以 dave 登入 →「我的團隊」:列出 alice、bob 的案件;可多選優先級和部門篩選。
#7Draft history hidden隱藏草稿紀錄Create a draft, edit it a few times, then submit. The audit trail and the PDF start at “Case submitted”.建草稿並修改幾次後送出;稽核紀錄及 PDF 從「案件已送出」開始。
#8PDFDownload Case on the case from 2.1: the PDF keeps the content formatting and lists the case type and custom fields (in English).在 2.1 的案件按「下載案件」:PDF 保留內容格式,並列出案件類型和自訂欄位(英文)。

04Good to know注意事項

Templates follow the initiator’s own department範本是依發起人本人的部門配對 — The template is chosen from the case type and the department in the initiator’s user profile, not the department picked on the case form. If no department template matches, the Default template applies; with neither, people are chosen by hand as before. 系統用「案件類型」加「發起人使用者資料裡的部門」挑範本,不看建案表單上選的部門。沒有對應的部門範本時套用預設範本;兩者都沒有,就照舊手動選人。
Moving to approval移至審批 — After the review stage finishes, the initiator clicks “Move to Approval”. The case does not move on by itself. This is the system’s original behaviour. 審閱完成後,要由發起人按「移至審批」,案件不會自動進入審批,這是系統原本的行為。
Email — Email only goes out if a mail server is configured for the demo site. Without one, the reminder reports “Email could not be sent”; in-app notifications still go out. 示範網站要設定郵件伺服器才會真的寄出 Email;未設定時,提醒會顯示「郵件寄送失敗」,系統內通知照常送出。
Editing submitted cases編輯已送出的案件 — Changing the content of a submitted case restarts the approval flow. This is the system’s original behaviour. 修改已送出案件的內容會讓審批流程重新開始,這是系統原本的行為。