← 返回教程首页 | 视频图文笔记 第 5 / 5 期

Workday 业务流程框架详解:定义复制与链接、安全策略、条件规则、待办与通知

Business Process Framework in Workday HCM | ZaranTech

频道:Workday Learner Community(ZaranTech) 时长 2:05:55 发布于 2024-09-07 34 帧对照 · 全片覆盖 原视频 ↗
⏱ 每节的 时间点 对应视频画面,点开原视频拖到该时间即可对照。
实际内容与标题相符:这是 ZaranTech Module 7 直播课录像,全程围绕 Workday HCM 的 Business Process Framework——BP 组成与默认/组织专属定义、Copy 与 Link 机制、BP 安全策略、步骤顺序与并行、条件规则、完成步骤语义、BP 流程图、Find Events 等报告、Edit/View 分工、通知配置,最后附带一段 Divide 与 Create Subordinate 的答疑。字幕为 YouTube 自动生成,错识较多(如 hire 被写成 higher、Workday 写成 work they、Acme 写成 acne、Logan McNeel 写成 log MC meal、business process 偶写成 business passes);正文一律用正确术语,quote_en 保持字幕原样,不改动语法。画面文字来自 ZaranTech 课件(Copyright 2020)与 Workday 演示租户截图,个别字段名以截图可辨认为准,看不清的已标(待核对)。
0:30

BP三要素与通知时机

BP三要素与通知时机
  • 幻灯片 Business Process Framework 左侧列出本模块五个主题:Configurable BPs、Business Process Definitions、Order of Execution、Rule Based Business Process、Notification
  • 一个 BP 由一串按顺序完成的任务(task/step)组成,全部走完业务事件(business event)才算发生
  • 每个步骤都可以指定负责的安全组(security group),组内成员收到待办并反馈完成情况
  • 通知可挂在四种时机:事件发起时、某个状态触发时、某个步骤完成时、整个 BP 完成时

"you could say when the event is kicked off when uh a specific um status is triggered when um a specific step is completed or when the whole BP is completed"— 你可以设置在事件被发起时、某个特定状态被触发时、某个特定步骤完成时,或者整个业务流程完成时(发送通知)。

4:00

未关联组织的默认回退

未关联组织的默认回退
  • 画面组织图:Global Modern Services 下辖 Executive Management、Finance Administration(含 Financial Planning、Legal),Legal 单独挂 Hire for Legal;右侧 Acme Corp 指向 Hire Default
  • 同一个 Hire 流程,Legal 团队可以有自己的专属版本:多加审批、待办或被触发的服务
  • 新建组织(如 Acme Corp)若不单独关联任何 BP,系统自动使用 Default Definition
  • 也就是说:不手动把 BP 绑定到组织结构,任务触发时永远去找挂在任务上的默认定义来跑,直到你手动覆盖它

"if you don't dictate or manually assign or link these BPS to your or structure it's just going to always go and um find whatever the default definition is that's tied to the task and kick that off until you manually kind of override it"— 如果你不指定、不手动分配或不把业务流程链接到组织结构上,系统永远会去找挂在任务上的那个默认定义来启动,直到你手动覆盖它。

5:00

BP挂到组织的两种方式

BP挂到组织的两种方式
  • 幻灯片原文:Workday 允许为特定监督组织(supervisory organization)建不同的步骤/工作流,例如 IT 用的 Hire 流程可以和 HR 用的不同
  • 覆盖默认定义的做法:复制一份下来,再在具体监督组织上做配置
  • 创建组织专属 BP 的入口在组织的 Related Actions 菜单:Business Process > Copy or Link Business Process Definition
  • 两个选项:Copy existing Definition(复制现有定义)或 Link existing Definition(链接现有定义)

"so you can go to the org do related actions specifically look for um business process copy and Link is um copy existing definition or link existing definition"— 你可以进入组织做相关操作,专门找 Business Process 下的 Copy and Link,也就是复制现有定义或链接现有定义。

8:15

全局BP与组织BP取舍

全局BP与组织BP取舍
  • 画面对照表:Default Business Processes 优点=推荐做法、维护容易;缺点=复杂条件规则拖慢处理
  • Organization-Specific Business Processes 优点=更易分析、复杂规则下性能更好;缺点=公共步骤要逐个 BP 加、每次更新都要测试
  • Finance 和行政各部门差异大(律师要走特定审批、财务规划师又不同)时,拆独立 BP 加条件,比在一个 BP 里给所有人堆步骤更干净
  • 小公司全员同流程适合一套默认 BP;Amazon、Walmart 这种规模大概率是组织专属 BP 配专职团队维护和测试

"it makes sense to just kind of split off um there BP and add condition rules maybe or other items here rather than constantly just adding all of those additional steps for everyone else and just making it more complex when you're trying to troubleshoot"— 把它们单独拆出一个业务流程、加条件规则或其他配置更合理,而不是一直给所有人追加步骤,让流程在排障时越来越复杂。

11:15

复制定义到具体组织

复制定义到具体组织
  • 幻灯片 Copying Business Process Definitions 给出操作路径:Related Actions 菜单选 Business Process > Copy or Link Business Process Definition,再选 Copy Workflow Definition to Business Object 选项
  • 示例提示框里要填 Time Zone(GMT-08:00 Pacific Time (Los Angeles))、Business Object(选 Global Modern Services, PLC (U.K.))、Effective Date(待核对,截图日期未辨清)
  • 演示的业务流程类型是 Customer Invoice Email Event:把当前定义复制到 Global Modern Services 名下
  • 复制后系统里并存两个独立版本:Customer Invoice Email Event (Default Definition) 与 Customer Invoice Email Event for Global Modern Services,步骤相同但互不影响

"they're saying is go ahead and copy the definition that's associated um the current business passes um BP and ass it with global modern services"— 它的操作就是:把当前(默认)业务流程关联的定义复制一份,挂到 Global Modern Services 上。(字幕把 business process 误作 business passes、associate 误作 ass)

13:45

BP安全策略五项权限

BP安全策略五项权限
  • 幻灯片定义:Business Process Definition = 组成流程的步骤(任务)清单 + 每步负责的角色
  • Business Process Security Policy 与域安全策略(domain security policy)平级,管五类授权:启动业务流程、执行业务流程内的动作步骤、对整个业务流程执行操作、批准/纠正/取消/重发步骤、转派任务
  • 谁做审批、谁触发集成,都是在策略里指定的安全组决定的
  • 步骤可挂多个安全组:默认组里一人办完即可,也可配置成组内人人必办
  • 与域策略一样:策略里改动安全组后必须激活(activate)变更才生效

"once you go ahead and add any um security groups on um the business uh process security policy you're going to go ahead and activate that as well"— 一旦你在业务流程安全策略上添加了任何安全组,你同样要去执行激活操作(变更才生效)。

17:00

执行顺序推荐小写字母

执行顺序推荐小写字母
  • 幻灯片:可配置执行顺序的四种对象——业务流程步骤的顺序、一个条件内多条规则(rules in a condition)的顺序、清单(checklist)内待办的顺序、步骤 help 的响应顺序
  • Order 列可输入一个或多个字母数字字符;按字符串排序时 10 排在 2 前面,所以不推荐用纯数字
  • Workday 交付的默认定义全部用小写字母 a、b、c、d 编号,推荐跟随
  • 用字母的好处:A 与 B 之间要插步骤时写 a1 或 aa 即可,不用重排既有步骤;大写不会阻止你使用,只是排序在其后

"just like I was saying 10 sorts before two so that's why kind of that's not recommended it's just using lowercase letters you'll see that when you're looking at the default definition"— 就像我刚说的,10 会排在 2 前面,所以不推荐那样用;就用小写字母——你看默认定义时也是这样的。

20:15

BP实用笔记四条

BP实用笔记四条
  • 幻灯片原文笔记1:搜索方法 bp: <输入流程名>,可直接定位业务过程
  • 笔记2:某个监督组织可用的所有 BP 都列在 Sup Org > business process 菜单下
  • 笔记3:往审批里加 Finance Executive 这类组,必须同时有域访问权且在该 BP 安全策略内;用 Business Process Security Policies for Functional Area 报告可查到策略所在功能区(如 Propose Compensation Hire 属于 Core Compensation)
  • 笔记4:完成步骤结束即整个 BP 显示为完成,哪怕后面还有步骤(新员工已算 hired,W-4 还没填);若没设完成步骤,则以最后一步的完成为完成
  • 条件规则的本质:不是命令流程「跳到第 D 步」,而是数据满足条件就执行挂在条件上的那个步骤,不满足自动走下一步

"it's going to be through condition you won't be able to say you know like you don't get to specifically say like go to step D it's really about does the information meet the criteria to meet that condition rule"— 这是通过条件实现的——你没法明确说「去第 D 步」,本质是看信息是否满足那条条件规则的标准。

23:45

BP日常运维操作清单

BP日常运维操作清单
  • BP 相关操作包括:修复业务过程、出错后重启、把流程挂起(hold)、转派具体步骤(如审批人休假或积压)
  • 对单个步骤的动作:批准、拒绝、退回(send back)、修改(revise)、跳过(skip);整体层面:取消、在某动作后关闭、纠正(correct)
  • 画面笔记页:当系统找不到被指派角色的用户时,会自动生成待办帮助你在组织里重新指派角色,审计里逐行核对步骤与所需角色
  • 用户若无转派所需的安全组成员资格,可发起 Request Reassignment,由 Business Process Administrator 批准后点 Reassign Steps 批量指派

"you can go ahead fix these business processes restart something like if there's errors put a business process on hold um you can reassign steps"— 你可以修复业务流程、在出错时重启某个流程、把业务流程挂起,也可以重新指派步骤。

27:45

bp:前缀搜出全部定义

bp:前缀搜出全部定义
  • 搜索框输入 bp: hire,返回 92 条业务过程定义:Hire (Acquisition)、Hire (Default Definition)、Hire (Simplified),以及 Hire for ABC - Global Manufacturing Department、Hire for CEO Group、Hire for Finance 等
  • 同一流程类型可以并存一个默认定义 + 任意多个组织专属定义,列表一眼能看出哪些组织定制过 Hire
  • 命名规律(画面印证):关联到某监督组织后,定义名称自动带上该组织名
  • 默认定义视图里同样能看到描述、可选审批动作(advance/resend/cancel 等)、可用任务、子流程等信息——Workday 里同一份数据总有好几个入口看

"you always have the default definition and once you go ahead and assign it to a specific supervisory or then you get the name of that supervisory or"— 你始终有一个默认定义;一旦把它指派给某个具体的监督组织,名称就会带上那个监督组织的名字。

28:15

并行步骤与Optional

并行步骤与Optional
  • Hire for Global Modern Services 步骤表:a Initiation;b Hire Not from Recruiting?(Action: Start a Background Check);c Country with Collective Agreements?(Assign Collective Agreement);d Propose Compensation Hire(Compensation Partner)
  • d 完成后,Order 同为 e 的两步(Request Stock Grant for New Hire、Request One-Time Payment)同时启动,都交给 HR Partner
  • 两步的 Optional 都是 Yes:不等待它们完成,流程直接推进到 f;若 Optional 设为 No,则并行步骤须全部完成才触发 f
  • f(Country with Works Council Staffing Approval?,Approval,组 Works Council)行的 Complete 列标 Yes——它是完成步骤;页面右上还挂着 1 Error 徽标(待核对具体内容)
  • g/g5 行显示 Service: Create Workday Account 与集成步骤(Run As User: IS_SPDC_UserProv)

"both of these are going to be kicked off at the same time and both are going to go to um the HR partner but you see over here because of configurations we sent this to optional so it's going to move forward to to f"— 这两步会同时启动、都交给 HR Partner;但因为这里的配置把(步骤)设成了 optional,流程会直接推进到 f。

29:45

谁可发起各雇佣场景

谁可发起各雇佣场景
  • 页面 View Business Process Security Policy - Hire,按「Who Can Start the Business Process」分组,逐条列出每个 Initiating Action 允许的 Security Groups
  • Hire Employee 场景当前 Security Groups 显示 (empty);Hire Employee (Web Service) 场景则授予 Amar_group_manager、HR Administrator、HR Partner、HR Partner (By Location)、HR System 及 More (5)
  • Convert to Employee(合同工转员工)单独一条策略,允许上述类似组,且「Security Groups who can delegate this action to others」为 MANAGER——经理可代发起
  • 讲解要点:Hire 这类复杂流程天然有多个发起场景(直接雇佣、转员工、Web 服务集成等),每个场景各自控制谁能启动,不在名单里的组就发起不了
  • 策略里的组不是系统自动建的:和域策略一样,先创建/维护安全组,再放进策略

"you see multiple kind of uh initiating steps and it's specifically for um you know what type of hire you're doing so maybe you're in this scenario converting a contingent worker to employee you want certain security groups to go ahead and access this"— 这里能看到多个发起步骤,分别对应你做的雇佣类型:比如合同工转员工这个场景,你会希望特定的安全组有权启动它。

32:45

安全组改动需激活

安全组改动需激活
  • 讲解核心:BP 安全策略里移除或添加安全组后,只有执行 Activate Pending Security Policy Changes 变更才生效
  • 谁能审批某个步骤,取决于他的组是否列在该 BP 策略里——不在列表里就看不到、办不了那步的待办
  • 画面步骤表下半段(滚动位置不同、信息不同):i Edit Government IDs、Add Probation Period(HR Partner)、j 条件「pay group 不在 payroll 接口且国家为 UK」触发 Assign UK Payroll ID(Payroll Administrator / Payroll Administrator-UK)
  • Onboarding Setup 一步同时挂 HR Partner 与 MANAGER 两个组(Group 列可见)
  • 右上弹窗提示 Request_One_Time_Payment.xml 已可在 My Reports 中获取——集成文件跑完后回落到报表

"really important just make sure once you make those changes they're only effective once you activate pending security policy changes"— 非常关键的一点:务必记得,这些改动只有在你执行了「激活待处理的安全策略变更」之后才会生效。

34:45

泳道图是排障神器

泳道图是排障神器
  • BP Definition for Visualization:泳道按安全组划分——AJ-user based sec grp(Initiation 绿圈)、HR Partner、Compensation Partner、Works Council(画面顶部还有 Related Business Process Defini... 下拉可切子流程)
  • 菱形 if = 条件分支:Hire Not from Recruiting? 为 Yes 走 Start a Background Check;Country with Collective Agreements? 为 Yes 走 Assign Collective Agreement,否则 No 弧线直接跳过
  • 这张可视化是 Workday 原生功能:在此功能出现前大家自己画 mockup,还大量提 support case 说「配置的和跑出来的不一样」
  • 加条件规则、加并行步骤之后流程变复杂,测试前先用图核对「我是不是真的按需求改对了」,这是最好的排障手段
  • 讲师顺带提到:这类策略/配置页没法直接打印,她过去只能截图再打印留档,麻烦但可行

"especially when you add the condition rules and you add all these parallel steps and stuff it's really important to kind of see a visual view right"— 尤其当你加了条件规则、加了一堆并行步骤之后,能有一个可视化视图来看(流程真实长什么样)就特别重要。

38:15

条件例:非招聘背调

条件例:非招聘背调
  • 页面标题即规则语义:IF Hire Not from Recruiting THEN Entry of b - Start a Background Check
  • 字段结构:Triggers Workflow Step = b - Start a Background Check;Condition Rule = Hire Not from Recruiting;Derived Logic = Job Application Business Process Created From is empty
  • Rule Conditions 表四要素:And/Or、Source External Field or Condition Rule(Job Application Business Process Created From)、Relational Operator(is empty)、Comparison Type(Value specified in this filter)
  • 该字段是 Workday 交付的:记录这次雇佣关联的求职申请(Job Applicant event)从哪创建,非空即代表来自招聘
  • 讲师现场点评这条配得不太好(「probably a bad example」)——判断来源为空的语义绕,示例仅作参考

"here's the name hire not from recruiting and basically the rule that I have is job application business process created from so where was and you could just go ahead click on um these this related action and then you'll get more information"— 规则名叫 Hire Not from Recruiting,用的字段是 Job Application Business Process Created From——也就是申请是从哪儿创建的;点这个相关操作能看到更多信息。

39:45

条件例:德国劳资委员会

条件例:德国劳资委员会
  • IF Country with Works Council Staffing Approval THEN Entry of f - Approval by Works Council
  • Derived Logic 显示两条判断用 Or 连接:(Country of Location - Current any in the selection list Germany)Or(Country for Location - Proposed any in the selection list Germany)
  • 即:雇佣对象当前所在国家是德国,或拟定工作地是德国,任一满足就多走一步 Works Council 审批,否则整段跳过
  • Comparison Type 是 any in the selection list,Comparison Value 填 Germany——关系运算符与比较类型由 Workday 提供,比较值才是你配置的
  • 满足条件时 HR Partner 会看到 Assign Collective Agreement 步骤,去指派对应的集体协议

"so if this person meets this criteria that they're before this business process kicked off that their um uh location was Germany or that their proposed location is Germany then they need to go ahead um and go through this uh this this step"— 如果这个人满足条件——在流程启动前他所在地是德国,或者拟定工作地是德国——那他就要走这一步。

45:45

每组织仅一个Hire BP

每组织仅一个Hire BP
  • 本页(步骤表滚到底部,徽标显示 26 items):i 段之后有 Assign UK Payroll ID、Onboarding Setup(HR Partner+MANAGER)、Add Mentor during Hire、j Maintain Employee Contract(条件 Country with Employee Contracts?)、Remove Retiree Status(条件 Employee is a retiree?)、Edit Service Dates(条件 Country is China or Hong Kong?)
  • 26 个条目不等于 26 个真实执行步骤:带 If 条件的分支不满足就跳过,同 Order 的并行步骤会并发
  • Step Label Override 列可以给步骤写长说明:Edit Service Dates 的覆盖标签为「Edit Service Dates - Add Total Work Experience & Months Continuous Prior Employment」(画面可见,个别词待核对)
  • 现场问答的关键结论:同一个监督组织在同一流程类型下只能有一个 BP——GMS 只能有一个 Hire 定义(Propose Compensation 等子流程可以另配多个)
  • 整个组织树可以有多个不同版本的 Hire:某个下级部门挂自己专属的那份即可

"that's really key you can't have a higher business process two higher business process for the same um and maybe I what I the supervisory or so for Global modern Services you should only have one Higher business process"— 这点很关键:同一个(监督)组织不能有两条 Hire 业务流程——对 Global Modern Services 来说,你只应该有一个 Hire 业务流程。(字幕把 hire 误识别为 higher)

59:15

创建复制链接定义页

创建复制链接定义页
  • Lab:页面 Create, Copy, or Link Business Process Definition 有四个必填项(红星):Effective Date、Time Zone、Business Object、Business Process Type
  • Business Process Type 决定给哪类流程挂定义:Hire、Termination、Propose Compensation 都是独立的类型,各配各的
  • 三个单选:Copy existing Definition(选中后右侧带出 Hire (Default Definition))、Link existing Definition、None of the above
  • 选 Copy existing 可以从任何一份现成定义复制(比如直接拿 GMS 那份步骤复杂的);本 Lab 故意选 Default Definition,拿到只有一个 Initiation 的空壳后手工加步骤
  • 选 Link existing 则与源定义联动:源改了这边跟着变,适合要求全租户一致的场景

"so I'm saying I want this higher higher and I want to copy from existing definition if I do none of the above it's going to look very similar to this it's just going to have an initiation thing"— 我的意思是:这个 Hire 我要从现有定义复制;如果选 None of the above,建出来的也基本就是一个只有 Initiation 步骤的空壳。(字幕把 hire 误作 higher)

1:05:15

Edit视图的边界

Edit视图的边界
  • Edit Business Process Definition - Hire for SairaTech(5 items):可编辑行内字段 Order、Parallel Step Inbox Order、If、Notes、Type(下拉选 Action/Service)、Specify、Optional、Group、Run As User、Due Date
  • 已加步骤:b Propose Compensation Hire(Action,HR Partner,1 Day);c Applicant has Workday Account?(Edit Workday Account,Security Partner);d Applicant does not have Workday Account?(Service: Create Workday Account);e Is there already an in progress Onboarding?(Onboarding,1 Week)
  • 坑:Edit 视图里 Complete 列勾不了、条件规则加不了、Label Override 也改不了——凡是「步骤级」配置都必须退出 Edit 回 View 做
  • 行左的 ⊖/⊕ 用于删行/插行;画面右上显示 2 Errors(角色未指派类,待核对具体报错)
  • 复制/链接时源定义的启动安全组与 BP 安全策略会一并带过来,不用再配

"so over here I can't do the options that I'll show you in a little bit so set a specific step to completion right like it's here but I can't check it for whatever reason and um you know the conditional stuff I can't add it here the um what is it um label overrides I can't do"— 在(Edit 视图)里做不了那些选项:把某步设为完成步骤——框就摆在这但没法勾;条件也加不了;label override 也改不了。

1:06:45

完成步骤该怎么设

完成步骤该怎么设
  • 退出 Edit 回到 View Business Process - Hire for SairaTech 后,选中步骤即可 Set to Complete;画面 d 行(Create Workday Account)的 Complete 列出现 Yes
  • 完成步骤的语义:流程一跑到这步就算 hire 完成——新员工此刻起可被搜索到、可建 Workday 账号,后面的 Onboarding(e 行,1 Week)继续在后台推进
  • 若不设这个 Yes,默认要等整条流程最后一步(step z)完成,人才算「入职成功」可检索——排障时找不到人先查完成步骤设在哪
  • c/d 两行构成有/无 Workday 账号的条件分支:有账号由 Security Partner 编辑,没账号走 Service 自动创建,两条路都会到达完成点
  • 步骤级功能(条件、label override、通知、完成定义)全都只在 View 模式下可操作

"as soon as it hits this step I'm basically saying go ahead and hire whoever this business process was kicked off for right and um the event is complete and I'll be able to search for this person in the system"— 一跑到这一步,等于在说:把这条流程对应的候选人正式雇佣掉——事件完成,我就能在系统里搜到这个人了。

1:09:45

并行步骤改错被拦截

并行步骤改错被拦截
  • 弹窗 Error - Page Error 原文:Some Steps are out of order: Step d (Service: Create Workday Account) must occur after the Completion Step(步骤顺序错误:d 必须排在完成步骤之后)
  • 弹窗 Alert - Page Alert 原文:Actions that start subprocesses may lead to unexpected results if executed more than once. Please ensure these actions will not execute multiple times: Propose Compensation Hire——启动子流程的步骤被执行多次会有意外结果
  • Workday 会直接拦下「两条并行步骤完全相同」的定义,必须让其一不同:这里给其中一条加 Label Override 改名 Renumeration
  • Label Override 只影响待办显示的标题,底层动作还是同一个步骤动作,收件人在待办里看到的是新名字
  • 页面右上徽标此时显示 1 Error and 1 Alert(待核对),修顺序、加覆盖标签后清零

"right now that they're parallel steps work days are going to stop you that you know it's exactly the same thing ... but what I want is for this one to be for something else so I'm going to do a label override call this renumeration"— 现在它们是并行步骤,Workday 会拦住「两条完全一样」的配置……我要让其中一条用途不同,所以做个 label override,改叫 Renumeration。

1:13:15

建条件先选对字段

建条件先选对字段
  • Create Condition Rule 页面结构:Description、Comment、Category、Derived Logic,下面是 Rule Conditions 表:And/Or、括号、Source External Field or Condition Rule、Relational Operator、Comparison Type(默认 Value specified in this filter)、Comparison Value、Order
  • 页面顶部就有 Copy Condition from Rule 字段:逻辑写得多时别重打,整条复制改一处
  • 在字段框里输入 location 会弹出海量候选(current、just location hierarchy 等),必须靠读描述和关联业务对象来挑
  • 本例选「new location hierarchy for the worker as of the effective date」,关系运算符用 any in selection list,比较值选 UK
  • 给 UK 分支加条件:命中 UK 层级的人走这条步骤,否则按条件不走(页面右上显示 Errors and Alerts Found 提示未填完)

"you saw that there's many different you know current there's just location hierarchy so you could just figure out which one you want"— 你也看到了,(搜 location)会出来很多个——什么 current 的、光 location hierarchy 就好几个,得自己弄清楚要哪一个。

1:15:45

步骤挂条件用复制

步骤挂条件用复制
  • Maintain Step Conditions 页:Workflow Step 必填(Hire for ...),Entry Conditions 表逐行选 Condition Rule——即条件规则建好后,要在这里挂到具体步骤上才生效
  • 多条 Entry Conditions 的组合逻辑标注为 IF ALL condi(tions):所有条件都命中,该步骤才执行
  • 复制现成规则的流程:Copy Condition from Rule 带出已有逻辑,只改 Comparison Value(本例把 UK 对应条件复制一份改成 United States),省掉重打
  • Effective Date 与 Time Zone 在条件维护页也要重填(画面显示 11/13/2...、GMT-08)
  • 条件规则可以想多复杂就多复杂,还能各自指派不同安全组:US 步骤给美国 HR Partner、UK 步骤给英国 HR Partner

"you could go ahead and copy like an existing one let's say you put a lot of logic in place and instead of typing it all up you can just do copy condition from rule"— 你可以直接复制一条现成的规则——比如你已经写了很多逻辑,不用全部重敲,用 Copy Condition from Rule 就行。

1:21:45

Lab成品:地域双分支

Lab成品:地域双分支
  • View Business Process - Hire for SairaTech(6 items)成品:两条 Order 同为 b 的分支步骤,If 分别是 Location Hierarchy US Saira? 与 Location Hierarchy UK Saira?(尾部带问号,画面截断待核对)
  • 两条 Specify 都是 Propose Compensation Hire,但 UK 那条用 Step Label Override 显示为 Renumeration SairaTech——同一动作在待办里以不同标题出现
  • Complete 列:只给其中一条设了 Yes,系统把两条都标成 Yes——互斥分支里命中哪条,哪条就作为完成点结束流程
  • c 编辑 Workday 账号 / d 创建 Workday 账号(Service)/ e Onboarding(1 Week)保持原样,Optional 均为 No
  • 页面右上剩 1 Alert(黄条),对应子流程步骤重复执行的提醒

"how do I know if something is kind of stuck in a BP so there's always that um you know you could go to the specific higher and look at"— 怎么知道某个流程卡在哪了——你总可以进到那条具体的 Hire 业务流程去看(当前配置与进展)。(字幕把 hire 误作 higher)

1:22:15

Find Events查卡哪了

Find Events查卡哪了
  • 报告按业务过程名称过滤(输入 hire),还能按发起人(worker initiates)、雇佣对象、状态(Status)切片;左侧 facet 显示 Business Process > Hire (591)(计数以画面为准,待核对)与 Organization、Status 分组
  • 每行就是一个 hire 事件:Hire: Maria C orderza / Logan McNeil | P-00011 Director, Benefit | 06/13/2007 这类格式,人名、职位、组织、日期一目了然(字幕/画面人名以可辨认为准)
  • 点进去能看到各步骤在哪一步、由谁完成、何时完成——回答「这个人入职卡在哪了」
  • 配套排查路径:先看 Job History、Worker History 里已启动的流程与位置,再用 Find Events 查雇佣为何被取消或撤回、某人发起过哪些雇佣
  • 典型用法:别人问「怎么搜不到这个新员工」,多半是完成步骤还没到,用这报告确认事件所处位置

"or you can use um did I have here find events right and over here it's asking you for the business process name let's do hire"— 或者可以用 Find Events 报告——它会问你业务过程的名称,我们输入 hire。

1:27:45

合并审批与配置报告

合并审批与配置报告
  • 幻灯片笔记5:Business Process Configuration 报告列出该流程类型可用的步骤类型——Approval、Checklist、Questionnaire、To Do、Service(Service 触发 Workday 自有处理,如 WD 账号创建、文档投递到外部服务器)
  • 笔记6 Consolidated Approval:连续多步同为一个人/一个组的审批,合并成一条待办通知发送,不用逐条处理
  • 合并链条会被打断:如 20 步里有 5 步连着都是 HR Partner,中途插一步给 Security Administrator,就只有前 3 步合并成一条
  • 笔记7:bp diagram(View Diagram)按泳道看流程;笔记8:Find Events 回答三问——这个 hire 什么状态?为什么被取消/撤回?某员工发起过哪些 hire?
  • 报告只是换视角:同一信息还能从 BP 页的 Services/Actions 标签页看到,用顺手的那个即可

"instead of sending one inbox item for each one of those it'll just go ahead okay the next five steps are all for the HR partner let me just send it all together as one inbox item one kind of notification in their inbox"— 与其每一步发一条待办,它会这样处理:接下来五步都是 HR Partner 的,那就合并成一条待办、一个通知发到他们的收件箱。

1:31:45

读懂BP类型身份证

读懂BP类型身份证
  • Business Process Configuration Options 报告(搜索 business process config options 打开),Filter by Business Process Type = Propose Compensation Hire
  • Subprocess Only = Yes:这个类型不能单独发起,只能作为其他流程的子流程存在;Description 写明「为新员工或新增工作指派薪酬(package、grade、grade profile、plans、amounts)」
  • Allowed Subprocess For 列:Add Additional Job、Hire、Propose Compensation Hire、Start International Assignment——它能嵌进哪些父流程
  • 开关 Return Business Processes for which the selected are allowed Subprocesses:选中=反查谁能容纳它,不选=只返回定义本身
  • Valid for Usages=Supervisory;Approvable/Ad Hoc Approvable/Cancellable/Rescindable 均 Yes;Approval Options 列出 Approve、Deny、Send Back;Allows Delete Incomplete Business Process=Yes

"subprocess only so this is saying that this can only be part of another uh BP"— Subprocess Only——这是说它只能作为另一条业务流程的一部分存在。

1:36:45

Edit与View分工表

Edit与View分工表
  • 幻灯片 Edit 列:加/删步骤、排步骤顺序、指派组(Assign group)、设到期日、把步骤标为 optional、要求组内人人必办(Require all to act on step)
  • View 列:创建条件规则、增加/维护步骤延迟(timing)、为特定组配跳过步骤、更改用户可见的步骤标签(label)、加通知、定义流程何时完成
  • 直接打开 BP 页面默认进 View,只能对步骤做上述动作;要动步骤结构得走相关操作进 Edit
  • 步骤挂两个安全组时可勾 All:不勾则任一组员办完、其他人待办自动消失;勾上则两个组(如 HR Partner + Security Administrator)人人有份、全部完成才推进
  • Edit 里新增步骤会自动按字母序重排(画面 5 items 表按 a-e 排列),倒序输入也会被系统纠正

"when you have two um uh what is it called two security groups listed here then you could say select all and everyone needs to go ahead and um the HR partner and the security let's say administrator"— 当这一步列了两个安全组时,你可以勾选 All,要求每个人都得办——比如 HR Partner 加上(假设的)Security Administrator。

1:39:45

并行待办倒序显示

并行待办倒序显示
  • 幻灯片步骤:1 编辑 BP 定义;2 在 Order 相同的各步骤的 Parallel Step Inbox Order 列填一个或多个字母(如 ca、cb、cc)控制并行步骤在收件箱的排序
  • Result:收件箱按 Newest on Top 排序时,Workday 显示并行待办的顺序与定义里指定的正好相反
  • 示例:定义里 ca Add Photo、cb Complete Form I-9、cc Change Emergency Contacts,收件箱呈现为 Change Emergency Contacts → Complete Form I-9 → Add Photo
  • 若先处理了其中一个并行步骤并保存,它与其他并行步骤的相对顺序就不再维持
  • 对齐办法(Next Steps):把收件箱改按 Oldest on Top 排序,或在 Parallel Step Inbox Order 列按反序书写

"workday displays the inbox step task in the opposite order specified in the business process definition if you sort your inbox by newest on top"— 如果你的收件箱按「最新置顶」排序,Workday 显示这些并行步骤待办的顺序,会和业务流程定义里指定的顺序正好相反。

1:40:45

Action步骤是什么

Action步骤是什么
  • 幻灯片 Common Business Process Step Types(ACTION 页):Action 步骤要么是可编辑业务过程数据的 review 步骤,要么是调用子流程的步骤;review 类似审批但允许改数据
  • 示例1:Change Organization Assignments for Worker 流程里,员工本人(Employee As Self)借 Action 步骤变更福利选择
  • 示例2:Change Business Title 流程里,经理先审员工头衔变更,再由 HR Partner 终批
  • 示例3:Expense Report 流程里 Expense Partner 每五张抽审一张,含 VAT 的转 Tax Manager 审税;示例4:Customer Invoice Email Event 里 AR 专员发邮件前审发票
  • 对照 To Do:只是提醒/活动(安排工位、办工牌),可归入 checklist,不办也不挡流程;Action/Approval 只要没设 optional 就会卡住下一步

"to do is just a reminder so action you're actually taking some sort of kind of right like action approval it's kind of going to hold up the next step as long as you don't have it set to optional"— To Do 只是个提醒;而 Action、Approval 这类步骤,只要没被设成 optional,就会把下一步卡住(必须有人处理才能推进)。

1:45:15

加通知三要素设置

加通知三要素设置
  • 案例:Hire 进入 Onboarding 步骤时通知经理——触发时机可用 On Entry/On Exit,Trigger on status 还能盯流程整体状态(completed、cancelled、corrected;集成场景常关心 completed with errors/failed)
  • 收件人可选一个组(本例选 Manager)或指定人;也可填外部邮箱,但页面警告:这等于授权 Workday 用可能不受保护的协议向该地址发信,需自查地址准确性
  • Email Message Content 的 Subject 与 Body 都是「Text / External Field」逐段拼装:正文里插入新雇员的 Legal Name 与 Full Name 字段
  • SMS Message Content:可用任意报表字段,但不支持附件和富文本,单条限 160 字符,超出会产附加费(页面原文警告)
  • 页面上方说明:报表字段无效或收件人无权限查看某字段值时,通知里显示 [Not Available]

"you can say if you want a group of people to get it or specific um what is it uh specific person so here we get to put manager"— 你可以选择发给一群人,或者(来问的话)某个具体的人——这里我们把收件人设成 Manager。

1:47:45

通知预览与字段替换

通知预览与字段替换
  • See Workflow Notification Preview 页:Workflow Notification 指向 MANAGER 组,Email Subject = Legal name,Email Body = Your new hire "Full Name" has been assigned onboarding tasks.,User Language = English (United States)
  • 引号里的字段名在真实发送时被替换成实际值:按示例雇佣 Sarah Nowak 时,主题显示其 Legal Name、正文变成 your new hire Sarah Nowak has been assigned onboarding tasks(人名以讲解为准)
  • 预览规则(页面原文):没有权限查看某字段值时显示 Not Available;数据后续有变,预览值与实际发出值也可能不同
  • 通知在 Notifications 标签页集中管理:可随时 Disable 停用、Edit 修改、复制、删除,也能从这里反向进入添加
  • 文案想写多长都行、能拉很多字段,但初配时拼装过程被讲师自嘲为 clunky(笨拙),要有耐心

"email subject is legal name email body is your new hire and then you know whatever you're seeing in quotations it's when this is actually being sent out"— 邮件主题是 Legal Name,正文是 Your new hire……你看到引号里的那些(字段),要到真正发送时才会被替换成实际值。

1:55:00

Divide与下级的区别

Divide与下级的区别
  • 答疑场景:学员问「建了监督组织 XYZ,往下 Create Subordinate 一个 X,又 Divide 一个 Y,这俩有啥区别」;画面 Org Chart 里 Exec Mgmt_Saira Department (0) 下挂 Fin & Admin_Saira Depart、Human Resources_Saira I..、IT_Saira Department(均 San Francisco)
  • 讲师现场以 Human Resources 为例:Create Subordinate 建 Benefits Department 提交,或改用 Divide 建 Payroll,两条路在组织树里看起来效果一样
  • 她当时的第一反应:两者「没有实质区别」,现场唯一注意到的是 Divide 时要多填新组织所在的 Location
  • 处理存疑问题的示范:不硬答,去 Workday Community 查官方文档、再回租户实测验证——下一帧给出纠正后的结论
  • 画面是 Org Chart 业务过程页:左上可切换列表视图、右上有打印图标;三张部门卡片均显示默认云形占位图标而非人名

"to answer your question succinctly or like in very few words is there's no real um like real difference you could do create so for human resources I could do create subord"— 简练地回答你的问题:(Create Subordinate 和 Divide)没有真正的区别——对 Human Resources 我可以做 Create Subordinate……

2:01:30

文档:Divide继承上级

文档:Divide继承上级
  • Workday Community 搜 divide 得 14 条结果,打开 Manage Workday 下的 Divide an Organization 文档(这就是讲师说的 admin guides 视角:告诉你功能为什么这样交付)
  • 文档定义:Divide 是「以业务过程方式创建一个新组织」,可指定把哪些下级组织搬进去;适用于 Supervisory、Company Hierarchy、Cost Center、Location、Region、Custom 六类组织
  • 操作步骤(文档原文编号 1-8):Reorganization > Divide Organization → Effective Date → Availability Date → 名称/代码 → Subtype → External URL → 勾选 Move to New Organization(或 Move All)→ Submit;Rescind 时新同级组织会脱离层级成为自由组织
  • 关键结论:新组织默认继承的是上级(superior organization)的角色——讲师当场认错修正,并提醒面试别说错
  • 教训:凭手感说「没区别」不如查文档+实测,Community 的 brainstorms/documentation 是排疑的第一站

"work they enables you to create a new C organization as a business process and so roet move so you get to do divide organization um the new organization inherits roles from the organization Superior um organization by default"— Workday 支持以业务过程创建一个新的(同级)组织并搬移下级……也就是 Divide Organization——新组织默认从上级组织(organization Superior)继承角色。(字幕自动生成,work they=Workday、roet move 为识别杂音)