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

Workday 导师班第 10 期:Non-Exec 薪酬 Grade Profile 三地配置收尾与 Compensation Eligibility Rule 的 A=B 写法实操

Compensation Grade Profiles and Plan Foundations | Workday HCM Mentorship | ZaranTech

频道:Workday Learner Community 时长 48:45 发布于 2026-07-16 30 段对照 · 全片覆盖 原视频 ↗
⏱ 每节的 时间点 对应视频画面,点开原视频拖到该时间即可对照。
标题与内容相符——片头主题卡明确写着 SESSION 10 / TOPIC: COMPENSATION GRADE PROFILES AND PLAN FOUNDATIONS,全片就是围绕薪酬分级的 Grade Profile 配置收尾与薪酬资格规则(Compensation Eligibility Rule)展开的导师班教学课,无标题党、无招生/报价/带货。【篇幅判断】48:45 中答疑与课堂互动占比偏高:00:03:30–00:21:30 约 18 分钟(近全片 40%)是围绕'系统如何判定新员工适用哪套区间/executive 如何定义/能否用 job category 打标签/自建 management level'的多轮学员问答,00:22:30 起才进入 A=B 规则写法主线,00:43:30 之后是学员租户练习、探索作业布置与下课答疑——纯主线实操约占一半,购买者需知前 20 分钟偏讨论。【与前几期关系】本片是薪酬分级上篇(e6mot_1Om_g《Compensation Grades and Visual Grade Framework》,尚未上线)的直接续集:上节已建 executive grade + 三地 grade profiles,本节开场当众重建 non-executive 版作复习,再补齐 eligibility rules;第 6 期 staffing 相关概念(Position/Job Management、hiring restrictions、supervisory org 继承等)本片完全不复述;management level 字段在讲 job profile 时介绍过,本片只复用其取值(1 Board of Directors…6 Manager)并补充'自建时是开放文本字段、可整体系自建'。【字幕与数字声明】YouTube 自动字幕术语误识较多:higher date 实为 hire date、work data delivered 实为 Workday delivered、great profile 实为 grade profile、口播 time time 实为 time type、QR executive eligibility 实为 Cure Executive Eligibility(租户前缀 Cure 被读成 Q),正文统一改用正确术语,quote_en 一律逐字保留字幕原样不改语法;口播把比较值念作 01012027,但画面及后续帧均为 01/01/2025,以画面为准并已在对应段写明。数字/字段名照画面与 OCR 逐字记录:Cure_AMS_Exec_Profile / Cure_AMS_N_Exec_Profile 的 Total Base Pay 分段值(40,000.00/56,448.00、46,250.00/67,580.50、52,500.00/76,713.00、25,000.00/36,530.00、28,750.00/42,009.50 等,OCR 个别位数模糊处标(待核对))、Effective Date 10/12/2025 与 10/01/2025、Date of Last Change 10/12/2025 06:50:43.074 AM、Job Code Cure12345、WQL Alias hireDateCompensation、Search Results (5)、Rule Conditions 1/3 items、三地区间口播值(AMS 25,000–45,000 EUR、Boston 40–60,000 USD、Singapore 30–50,000 SGD)。【画面丰富度】屏幕共享(Workday 租户)+ Miro 白板交替,画面信息密度高,30 段均有独立可读画面,无'极少画面需置灰'的情况。
0:00

开场主题卡与作业检查

开场主题卡与作业检查
  • 片头主题卡:ZaranTech WORKDAY HCM MENTORSHIP PROGRAM Training,SESSION 10,TOPIC: COMPENSATION GRADE PROFILES AND PLAN FOUNDATIONS——与视频标题一致,证实是导师班系列第 10 期。
  • 开场检查上节课作业:是否已建 non-executive grade 及 executive/non-executive 作业,目前只有 Mahesh 回复;有学员称要明天补练,讲师要求至少先练一遍。
  • 承接上篇:上节已建 executive compensation grade 并为三个地点加了不同区间的 grade profiles;本节先当众重建 non-management 版,给还没做完的学员做示范。
  • 配置计划口播:payment segments 仍保持 4 个,grade profiles 建 3 个——已完成的学员当复习。

"Were you guys able to create the non-executive grade as well?"— 大家把非管理层的 compensation grade 也建出来了吗?

2:15

三地 Profile 连建

三地 Profile 连建
  • 画面 Grade Profile 弹窗:Pay Ranges 表头 *Compensation Basis / Calculate Segments / Minimum / Segment 1 Top…Segment 4 Top;左侧字段 Compensation Grade Profile Name *(输入 Cure_Boston_N_Exec_p…)、Compensation Grade Profile Description、Base Pay Elements *、Eligibility Rules *;左下 Inactive 复选框,OK/Cancel。
  • (含 00:01:45 合并)AMS 非管理版配法:Base Pay Element=Standard Base Pay、currency 欧元、frequency monthly,非管理区间 25,000–45,000 EUR、分 5 段均分(口播),同样步骤用加号再建 Boston。
  • Boston 版:eligibility rules 选 Boston、currency USD,区间口播 40 to 60,000;随后最后一个建 Singapore。
  • 画面字段全部带必填星号的只有名称、Base Pay Elements、Eligibility Rules(及 Pay Ranges 内的 Compensation Basis)——即一个 profile 最少要绑定'元素+资格规则+币种区间'。

"the range is 40 to 60,000 which last but not the least"— 区间是 40,000 到 60,000;最后一个(新加坡)……

2:45

Singapore 版与伏笔

Singapore 版与伏笔
  • 画面弹窗字段实值:Base Pay Elements * = Standard Base Pay、Eligibility Rules * = Location - Singapore、Currency * 与 Frequency * 空待填;下方 Pay Ranges 行 Total Base Pay + 6 个 0 值输入格。
  • Singapore 版口播:currency 用 SGD、区间 30 to 50,000 SGD。
  • 关键伏笔:eligibility rule 用 country Singapore 还是 location Singapore 有区别——讲师说 put a pin in that,等讲 eligibility 时再展开(与后文 00:24 的 country Singapore 案例呼应)。
  • 至此不到 5 分钟又建成一套 grade + 3 个 grade profiles;两套 grade 的差别只剩 money component(reference ranges / pay ranges)。

"Singapore see there's a difference if I use country Singapore and location Singapore right let's put a pin in that we'll discuss it once I complete setup"— 注意,用 country Singapore 和 location Singapore 是有区别的——先按下不表,配置完再讲。

3:30

新 hire 落哪套区间

新 hire 落哪套区间
  • 画面双栏对比:左 Cure_AMS_Exec_Profile(Total Base Pay:Minimum 40,000.00 / 56,448.00,Segment 1 Top 46,250.00 / 67,580.50),右 Cure_AMS_N_Exec_Profile(25,000.00 / 36,530.00,28,750.00 / 42,009.50…),Eligibility Rules 均为 Location - Amsterdam(数值照画面 OCR,个别位数模糊(待核对))。
  • 核心提问:新员工 hire 在 Amsterdam,系统怎么知道该给 executive 区间还是 non-executive 区间?此刻两套 profile 除 pay range 外几乎相同、setup 尚未完成。
  • 学员答'是 eligibility rule'方向正确;location 已覆盖(Amsterdam/Singapore/Boston 三地都有规则),缺的是'谁是 executive'的判定条件。
  • (含 00:04:30 合并)讲师纠正:director/manager 这些不是 positions,是 management levels——缺失的环节正是挂在 job profile 上的 management level 驱动的 eligibility rule。

"how will the system know that whether they should be eligible for this range which is for executive or whether they should be eligible for this range which is for non-executive"— 系统怎么知道新 hire 该适用 executive 的区间,还是 non-executive 的区间?

5:45

Management Level 取值

Management Level 取值
  • 画面左:Edit Job Profile 的 Category Details——Job Category 空、Management Level * 下拉已选 6 Manager,候选 1 Board of Directors / 2 Chief Executive Officer / 3 Executive Vice President / 4 Vice President / 5 Director / 6 Manager,另有 Job Level 与 Critical Job 复选框。
  • 画面右:并排打开的 Compensation Grade Profiles 表(Total Base Pay 25,000.00/28,750.00… 与 36,530.00/42,009.50…,OCR 低位模糊(待核对))——讲师把 job profile 与 grade 两页并排讲关联。
  • 讲师:management level 是 job profile 里的字段,1–8 为 Workday delivered(口播'From 8 till 1 is Workday delivered',表述含糊(待核对)),也可以自建自己的体系,但本用例没必要。
  • 方法论提示:把这些跨模块关联点串起来,能显著提升对系统的整体理解。

"As I scroll down, in the category details you will find something as management level. And there you will see board of director, chief executive, executive vice president, vice president."— 往下滚,在 category details 里会看到 management level 字段,里面有 board of director、chief executive、executive vice president、vice president 这些值。

7:30

Executive 划定与 Default

Executive 划定与 Default
  • 画面同一 Management Level 下拉页的手写标注完成态:2/3/4(CEO、EVP、VP)被圈出为 executive,1 Board of Directors 被划掉——公司不招董事会级别,最高只到 CEO 层。
  • 用例约定:hire 在 chief executive / vice president 等 management level 的人 → executive grade profile;director、manager、supervisor 及以下 → 自动算 non-management/non-executive。
  • (含 00:07:00 合并)两套 grade(executive / non-executive)此前只差区间,现在补上区分因子:management level → eligibility rule。
  • 评估顺序口播:规则放 grade profile 的 default 段,系统先评估 default 值(是否够 executive 格),再往下按 location 匹配区间——因字段必填(mandate)必须先填上。

"since this is a mandate, I'll put this as going back to our grade profile section. So, in this case, we'll put that eligibility rule in our default"— 因为这是必填项,我回到 grade profile 段——把 eligibility rule 放到 default 里。

8:30

薪资由资格规则驱动

薪资由资格规则驱动
  • 画面 View Compensation Grade「Cure Executive Grade」:Effective Date 10/12/2025、Inactive、Compensation Grade Description (empty)、Referenced by Compensation Package (empty)、Next Effective Dated Change;右侧 Compensation Grade Profiles 3 items。
  • 闭环讲解:你入职时被关联了 location,你的 job profile 挂着 management level,eligibility rule 驱动了 compensation、定下 range,你的工资最终在 range 里落定。
  • 结论句:compensation eligibility rules 是 primary drivers,一切由它驱动。
  • 系统评估顺序:先看 default 段的 executive 资格,匹配则再按 hire 的 location 决定 reference range(不限于新 hire,跨地点/跨级别调动同样触发重评)。

"It's because when you got hired, you were associated with the location. There was a management level associated with your job profile, and based on the eligibility rule, your compensation was driven, and the range was decided, and within that range, your salary was concluded."— 因为你入职时关联了 location,job profile 上挂着 management level,eligibility rule 驱动了你的薪酬、定下了区间,你的工资就在这个区间里落定。

10:30

自建级别之问

自建级别之问
  • 画面左:Compensation Grade Profiles 表(Base Pay Elements Standard Base Pay、Eligibility Rules Location - Amsterdam、Currency 列、Calculate Segments/Minimum 列头可见);右:Detail——Compensation Grade Name「Cure Non-Executive Grade」、Effective Date 10/01/2025、Referenced by Compensation Package (empty)。
  • 学员追问:新建 management level 时系统怎么知道它是 executive 还是 non-executive?按编号吗(新建会是 9 号)?——讲师(tl 续):自建不必沿用 Workday 的 1–8 编号,新 management level 名是开放文本字段,可完全自定义命名体系。
  • 另一学员补充实战经验:executive 的定义因客户/项目而异(有的公司 level 1–3 就算 executive)——讲师认可:executive 只是叫法,背后起作用的是挂到 job profile 上的 management level。
  • 画面印证:此帧 Non-Executive Grade 的 profiles 表里 Eligibility Rules 仍是 Location - Amsterdam(尚未换成自建规则)。

"Where do Where do you designate that against the management level that it's an executive or a non-executive position?"— 那你在哪里把一个 management level 标注成 executive 或 non-executive 的?

14:00

Miro 薪酬全景图

Miro 薪酬全景图
  • 画面 Miro 白板「CORE COMPENSATION」全景:Compensation Package = Compensation Grade(Reference Range Min-Max,下挂 Grade Profiles)+ Compensation Plan(Salary Plan/Hourly Plan、Allowance Plan、OTP plan,下挂 Plan Profiles);大括号把左右归并到「Compensation Eligibility Rules (Driver)」。
  • 图上还有 Localization 圆圈与 job profile → new hire 流向;job profile 左侧列着 Ceo / Director / associate / manager 级别,表示级别经由 job profile 带给新 hire。
  • 学员问'有没有个 tag 能标 director 及以上就算 executive,好让 bonus 自动加上'——讲师回答:job profile 就是那个 tag、那个 link,management level 就在 job profile 上关联。
  • 反证法:谁能招一个没有 job profile 的员工?没有——job profile 带着全部信息给新 hire,员工因此天然带上 executive/non-executive 的级别归属。

"The job profile is the tag. This is the link"— job profile 就是那个 tag,就是(我说要找的)那个关联。

15:45

NASCAR 例:头衔与级别

NASCAR 例:头衔与级别
  • 画面 View Job Profile:Job Profile Name「Cure Workday Analyst - 2」、Job Code Cure12345、Include Job Code in Name No、View As Of 10/12/2025、Date of Last Change 10/12/2025 06:50:43.074 AM;Management Level「4 Vice President」被高亮选中;Job Family「Cure Workday Family」;Job Category (empty)。
  • NASCAR driver 例:建画像时给它挂 management level;hire 后此人对外 business title 是 NASCAR driver,后台的 management level(如 vice president)只有 admin 和有高级权限的人可见。
  • 学员顺势追问:management level=vice president 之后,又在哪里把 VP 标成 executive 级?——引出下一段'executive 只是措辞'的回答。
  • 此帧同时是第 9 期 job profile 建设成果的回看:Job Family 已是 Cure Workday Family(上期作业产物)。

"So, when you will hire this person, they'll get a business title of NASCAR driver, and they're behind the scenes their management level, which will only be visible to admins and someone who has some senior access. That they're a vice president."— 雇这个人时,他的 business title 是 NASCAR driver,而幕后的 management level(他是 vice president)只有管理员和有高级权限的人能看到。

20:00

Job Category 建议被否

Job Category 建议被否
  • 画面 Job Profile 字段清单(滚动到中部):Management Level「4 Vice President」、Job Family「Cure Workday Family」、Job Category (empty)、Job Classifications (empty)、Work Shift Required No、Public Job No、Referral Payment Plan (empty)。
  • (含 00:19:00 合并)学员建议:要给 executive 发 car allowance,可以在 job profile 上加 job category=executive 的 tag,报表里筛 job category is executive 就能拉出人群——讲师否决:我们用的是 eligibility rules,job category 不能用于这个,那是另一回事。
  • 讲师纠偏:executive 不是字段、是概念;后台驱动 compensation 的是 job profile 上挂的 management level,不是你管它叫什么——画像里 Job Category 确实空置,画面与结论一致。
  • grade 名只是措辞:把 Cure Executive Grade 改名 Cure Senior Management Grades 也行,还可以建 senior group / junior manager group 各配不同区间——配置里定死的只有 management level 与 profiles 的关联;学员请求演示自建 management level,讲师说那要建整套(hierarchy+levels),留到下节课。

"The names are not set on stone. What is set up in the configuration is the management level and the profiles. That is the connection that we are having."— 名字不是刻在石头上的;配置里真正定下来的是 management level 和 profiles——这才是我们建立的关联。

21:00

两处规则的边界

两处规则的边界
  • 画面 Edit Compensation Grade「Cure Executive Grade」(顶部搜索框输入 grade profile):Effective Date 10/01/2025、Additional Information——Referenced by Compensation Package (empty)、Next Effective Dated Change、Done 按钮。
  • 学员确认理解:compensation profile 里目前最多组合两条 eligibility rules——第一条在 default,第二条在 compensation rate profile——讲师认可“for now”是这个程度。
  • 复杂场景是否要用 calculated field 重写规则?讲师:calculated fields not yet——还没讲到那一步。
  • 讲师预告:稍后会现场测试整套 setup,验证关联效果。

"understand that at most, we only have kind of combine the two two eligibility rules. The first one is in the default, and the second one is in the compensation rate profile."— 理解为:目前最多组合两条 eligibility rules——一条在 default,另一条在 compensation rate profile 里。

24:00

A=B 入门与 Singapore 例

A=B 入门与 Singapore 例
  • 画面 Miro 白板:顶部标题「Compensation Eligibility Rule」,A = B 三框横排,第一行条件 hire date ≥ 01/01/2025(>= 圆圈正被选中编辑,其余行还空着)。
  • (含 00:22:30 合并)讲师的'5 岁都懂'入门:需求语句'hire date 应大于 2025/1/1'——hire date 是 A、greater than or equal 是操作符、1/1/2025 是 B;99% 的资格需求都是这种语句,学员要参与拆解。
  • 第二个语句:任何 hire 在 country Singapore 的新员工有 X/Y/Z 资格——A 是 hire country(或 work country)、B 是 Singapore;学员先猜 location city / hire city,讲师强调'我说的是 country'。
  • 第三个用例抛出:hire date > 1/1/2025 + country=Singapore + employee type=full time——为下一段'复用规则'铺垫。
  • 字幕勘误:口播/字幕的 higher date 实为 hire date(画面框内写的就是 hire date)。

"Again, keep listening. Very important. I said anyone hired in the country Singapore."— 再听一遍,很关键——我说的是 hired in the country Singapore(国家,不是城市)。

25:30

复用规则加 time type

复用规则加 time type
  • 画面白板新增第二行:Country = Singapore(等号圆圈),与第一行 Hire Date ≥ 01/01/2025 并排框成一个条件组。
  • 解法演示:把已建的「hire date + country」规则整条当作 A、操作符 equal to true——true 即代表那两个条件都为真;再加一行 time type = full time 完成三条件。
  • 核心规则:现有 eligibility rule 可以被另一条 rule 复用——已有覆盖 hire date+country 的规则就不必重建。
  • 命名示范:组合规则可起名 hire date plus country,便于复用时识别。

"So, what I'll do is I'll actually use this existing eligibility rule as a value of A equal to true, which means that if this condition is true, this condition is true means both of them are being true."— 我要做的,是把已有的 eligibility rule 直接当作 A、等于 true——它为真就意味着那两个条件都为真。

27:30

类型匹配与全 Workday

类型匹配与全 Workday
  • 画面白板完成版:标题 Compensation Eligibility Rule、A = B;行1 Hire Date ≥ 01/01/2025、行2 Country = Singapore、行3 Hire Date + Country = TRUE、行4 Time Type = Full-Time,右侧独立框「Hire Date + Country」标出被复用的规则。
  • (含 00:26:30 合并)取反写法:若要 hire date 不大于 1/1/2025 且 country 不是 Singapore,把操作符换成 not equal to 即可——纯基础逻辑。
  • 方法论:先找 value of B(常量:日期、Singapore、true/false),再去配 value of A;A 字段必须与 B 类型匹配——date 型对日期、country 型(single instance/self-referencing)对国家、对规则等值用 Boolean(true/false)。
  • (含 00:28:30 合并)普适性结论:A=B 不止用于 compensation——condition rules、eligibility rules、alert rules、report filters 全是 A equals B;系统里'equal to'实际显示为 any in the selection list 之类的措辞。

"you need to understand this field is of type date, okay? This field is of type country. This field is equalizing with an eligibility. This field is of type single instance."— 要理解这个字段是 date 类型、这个是 country 类型、这个是在跟一条 eligibility 规则等值(single instance)——A 的类型必须对得上。

29:45

实操入口选类型

实操入口选类型
  • 画面租户首页(Hi There、Check In/Check Out、My Time Clock History、Team Highlights:Aishwarya RH / Akram Malik / Anu hr、Announcements 1 of 5、Important Dates;右上 It's Sunday, October 12, 2025),顶部搜索框正在输入 create comp eligi rule。
  • 讲师:eligibility rule 有多种类型——benefit eligibility、time tracking 等——所以搜索时必须先写 compensation,选中 Create Compensation Eligibility Rule。
  • 为什么要指定类型:value of A 所用的字段只能在 Workday Compensation 域里用,别的域用不了(由字段的 authorized usage 决定,下一段画面印证)。
  • 从最基础的做起:先建刚才加在 grade profiles 上的那几条资格规则。

"Hence, there are multiple types of eligibility rules that you can create, as you can see. Benefit eligibility, time tracking, many types of."— 资格规则有很多种类型——福利资格、工时跟踪等等——所以必须先写 compensation 来选定类型。

30:45

三要素对照 A=B

三要素对照 A=B
  • 画面 Create Compensation Eligibility Rule:Description * =「Cure - Boston」、Comment、Category、Derived Logic (empty)、Copy Condition from Rule;Rule Conditions 1 item(待填)。
  • 红笔标注映射:*Source External Field or Condition Rule 列下手写 A,*Relational Operator 列下手写 =,Comparison Value 列下手写 B;Comparison Type 列被打叉——留到报表章节再讲。
  • 系统要求顺序:先填 A(选字段)、再选操作符,然后 B 的值框才会打开——此刻 Comparison Value 还空着就是演示这一点。
  • 记忆法:source external field or condition rule / relational operator / comparison value 三列就记成 A equals B。

"So, for now, source external field or condition rule, relational operator, and comparison value."— 现阶段记住三要素就行:source external field or condition rule、relational operator、comparison value——就是 A 等于 B。

32:00

Hire Date 字段详情

Hire Date 字段详情
  • 画面字段详情弹窗(Hire Date (Compensation) 的 related actions):Business Object「Compensation Rule Targetable」、Description「Returns the applicable hire date.」、Field Source Workday Delivered、Field Type「Date」、Category Compensation Eligibility / Employment、Authorized Usage「Compensation Eligibility」、WQL Alias hireDateCompensation。
  • 关键规则:authorized usage 只列 Compensation Eligibility——如果建的是 benefits eligibility rule 或 recruiting eligibility rule,就不能用这个字段(会有另一个专用字段,甚至不在这份候选里出现)。
  • 检索方法:字段成千上万,初期靠 hit and trial;没人要求你造字段,你要会'找'字段(画面正是搜索 hire date 后点开 related actions 阅读)。
  • 字幕勘误:口播'work data delivered'实为 Workday delivered(Field Source 列画面原文)。

"The field type is date, and you will find in the authorized usage, it says compensation eligibility, which means let's say if I'm creating a benefits eligibility rule or a recruiting eligibility rule, I cannot use this field."— 字段类型是 date;authorized usage 写着 compensation eligibility——也就是说,建福利或招聘资格规则时不能用这个字段。

33:00

选操作符后值框才出现

选操作符后值框才出现
  • 画面规则行:Source External Field = Hire Date (Compensation),Relational Operator 选中「greater than or equal to」(蓝框),Comparison Type「Value specified in this filter」,Comparison Value 显示 MM/DD/YYYY 日期选择框。
  • 好习惯:点“All”看全部操作符——frequently used 只给少数几个;date 字段的完整候选是 is blank / is not blank / equal to / not equal to / greater than or equal to 等。
  • 细节演示:概念里的 equal to 与系统实际值不完全一样;选 greater than(不含等于)时比较值框不出现,选 greater than or equal to 后才出现,且只能输入日期。
  • 数字声明:口播把日期念作 01012027,但画面值框与后续帧(00:36:15、00:38:45)均为 01/01/2025——以画面为准。

"So, you wanted greater than or equal to Now, when I added this, let me remove this. You see the comparison value does not come up. But when I add this greater than or equal to, then only this value comes up."— 你要的是 greater than or equal to——注意:选不含等于的操作符时比较值框不出来,选了 greater than or equal to 之后值框才出现。

33:45

country 字段五候选

country 字段五候选
  • 画面搜索 country 的 Search Results (5):可见 Country of Location Current Otherwise Last Known Location (Compensation)、Primary Address - Country (Compensation)、Work Address - Country (Compensation),另两项被折叠;规则第一行 And 已是 Hire Date ≥ 01/01/2025。
  • 取舍法:先排除结尾不带 compensation 后缀的字段——别的域的字段拿过来也没用。
  • 初步候选:Country of Location(primary / current otherwise last known)、Primary Address Country、Work Address Country——可用其一,差别在字段类型(看字段图标:圆点加三点的即 multi-instance)。
  • 讲师放大字体让学生看清图标差异,为下一段 multi-instance vs text 铺垫。

"So, first we can rule out the ones which don't have a compensation suffix in the end. No point of using them."— 第一步先把结尾不带 compensation 后缀的字段排除掉——用了也没意义。

34:45

Text 型字段差异

Text 型字段差异
  • 画面字段详情弹窗:Business Object「Compensation Rule Targetable」、Description「The country from the work address for the worker. If the work address is blank, then uses the country of the primary address from the worker's location.」、Field Source Workday Delivered、Field Type「Text」。
  • 对比口播:multi-instance 的 Country of Location Primary 描述是'有 primary location 时返回其国家,否则返回所有 location 的国家',authorized usage 同为 compensation eligibility;两个候选都能用。
  • 决定:把两个字段都加进规则、一行一个,现场比较差异(下一段画面即两行并排)。
  • 画面下方规则行可见 And 行已就绪,右侧 Search Results (5) 面板仍在。

"Now, this field is of different type. It's of type text. This one says, "The country from the work address of the worker. If the work address is blank, then use the country of the primary address.""— 这个字段类型不同,是 text 型。描述说:取 worker 工作地址的国家;若工作地址为空,则用其 primary address 的国家。

35:15

multi-instance 操作符

multi-instance 操作符
  • 画面 Rule Conditions 3 items:行1 Hire Date (Compensation) greater than or equal to 01/01/2025;行2 Country of Location - Primary (Compensation)——All 操作符下拉展开(count is not equal to / count is greater than / count is greater than or equal to / count is less than…);行3 Work Address - Country (Compensation)。
  • multi-instance 字段的 equal to 变体:Exact match / not exact match / subset / count——count 用不上;multi-instance 场景下「any in the selection list」就相当于 equal to。
  • 选中后值侧出现下拉(三条横线图标),可搜索并直接勾选 Singapore——这是第一种填法。
  • text 型字段的操作符则是另一套:is blank、equal to、not equal to、contains、does not contain、starts with、greater than、less than(口播)。

"Since this is a multi-instance field, the value of equal to looks a little different. Exact match, not exact match, subset, count."— multi-instance 字段的 equal to 长得不一样:Exact match、not exact match、subset、count。

36:15

资格规则大小写敏感

资格规则大小写敏感
  • 画面 Rule Conditions 3 items 实值:行1 Hire Date (Compensation) greater than or equal to 01/01/2025;行2 Country of Location - Primary (Compensation) any in the selection list → Singapore(对象选择);行3 Work Address - Country (Compensation) equal to → 手输「singapore」(全小写,编辑中)。
  • text 型的风险:值要手动输入,若系统里叫 SGB、或实际写作 Singapore/全大写,就会匹配失败——Workday 一般不区分大小写,但 eligibility rule 里区分大小写。
  • 结论:非必要不用 text 字段;优先用带下拉/对象选择的字段(箭头图标表示系统里的真实 object/element)。
  • 讲师示范的两种填法并存:multi-instance 行用勾选、text 行用手输——正好对照。

"In general, Workday is not case-sensitive, but in case of eligibility rules, it is case-sensitive."— Workday 一般不区分大小写,但在 eligibility rule 里是区分大小写的。

38:45

AND 三条全真

AND 三条全真
  • 画面 Rule Conditions 3 items,And/Or 列三行均为 And(红笔圈注 Each And 并画箭头指向各条件):Hire Date (Compensation) greater than or equal to 01/01/2025;Country of Location - Primary any in the selection list Singapore;Time Type (Compensation) any in the selection list Full time。
  • (含 00:37:45 合并)Time Type 字段同样先点 related actions 读描述/类型/authorized usage——'读到第十遍总会有点懂';操作符 any in the selection list,下拉给出 Full time / Part time / Temporary,选 Full time。
  • AND 语义:系统按行顺序评估,只有三行全 true 才接受该资格——入职日期大于 1/1/2025、国家新加坡、full time,缺一不可。
  • 画面右下角「Updates are available / Required updates need to be installed」系统弹窗与配置本身无关。

"Only if all three conditions are true then only the system will accept that eligibility which means the employee must be hired greater than 11 2025, the country must be Singapore and the time time must be full time."— 只有三条全为真,系统才接受该资格——入职日期大于 1/1/2025、国家是新加坡、time type 是 full time,缺一不可。

39:45

OR 与括号

OR 与括号
  • 画面同一规则:第三行 And/Or 改为 Or(下拉可见),And 行仍为 Hire Date ≥ 01/01/2025 与 Country of Location - Primary = Singapore;第二行的括号列(( )被红笔圈出——每行左右都有括号位。
  • Or 语义:前两行都 true 当然合格;即便前两行不全 true,只要 or 之后的条件为 true,系统也判 eligible。
  • 括号用法:想保证第一行(hire date > 1/1/2025)必须执行,就在它两侧加括号——系统先评估括号内,再让 country 与 time type 二选一。
  • 讲师:这些就是建 eligibility rule 的各种变化(variations),先从最简单的建起。

"So what this will do is this system will evaluate that the higher date must be greater than 11 2025. That must be true. Now out of these two the country and time type anyone is true the system will consider that as eligible."— 这样系统会先保证 hire date 大于 1/1/2025 必须为真,然后 country 和 time type 两个里任意一个为真就算合格。

41:30

Q Boston 值搜索

Q Boston 值搜索
  • 画面 Create Compensation Eligibility Rule「Cure - Boston」:Source External Field =「Location - Primary (Compensation)」(检索词 primary location 命中),操作符 any in the selection list,Comparison Type「Value specified in this filter」,值侧弹出 Search for Value / By Location Type 搜索面板。
  • 为什么搜索只返回地点:value of A 是 location,搜索就只给 locations——不会蹦出 supervisory organizations、location hierarchies 或 grade profiles。
  • 输入 Q 列出全部 Q 开头的地点,选「Q Boston」并 OK,规则即保存可用。
  • 讲师顺带吐槽租户卡顿(system is running a little bit slow),帧里 Comparison Value 面板是等待后弹出的。

"Because the value of A is location. So, it will only give you in the search the locations. So, in this case, I'll use Q Boston and click okay."— 因为 A 是 location,搜索就只会给你 location——不会给 supervisory organization 或 location hierarchy。这里选 Q Boston,确定。

42:15

复制条件建 Amsterdam

复制条件建 Amsterdam
  • 画面 Create Compensation Eligibility Rule:Description * =「Cure - Amsterdam」、Comment、Category、Derived Logic (empty)、Copy Condition from Rule(空)、Rule Conditions 1 item(空行待填)、OK/Cancel。
  • 场景设定:假设你是公司新人、不熟命名规范,但知道其他地点已有规则——用 Copy Condition from Rule 填入 Q Boston,系统带出它用过的字段。
  • 操作:只需把带出的 Q Boston 换成 Q Amsterdam(先减号删旧值再换)——比从头建快得多(口播 It took me less time than the other one)。
  • 同法再建最后一条 Q Singapore:把 Boston 换成 Singapore 即可。

"So, I can actually use this option, copy condition from rule, okay? In which, I'll simply add my con- Q Boston here, and the system will give me what fields I have used."— 可以用 copy condition from rule:把 Q Boston 填进来,系统会带出我用过的字段,换个地点就行。

43:00

回填 Grade Profiles

回填 Grade Profiles
  • 画面 View Compensation Rule「Cure - Singapore」:Derived Logic「Location – Primary (Compensation) any in the selection list Cure Sin…」、Rule Conditions 1 item(And / Location - Primary (Compensation) / any in the selection list / Cure Singapore)、Rule Usage 页签;背景搜索框输入 edit comp grade(候选 Edit Compensation Grade / Edit Compensation Grade Profile / Compensation Grade 报表)。
  • 回填操作:回到 compensation grade profiles,编辑刚建的 Cure Executives(executive 与 non-executive 两侧都要),把三条 profile 的 eligibility rules 分别换成 Q Amsterdam / Q Boston / Q Singapore。
  • 目的:这样在所建地点雇人时,员工就会命中我们提供的区间(ranges)。
  • 随后布置练习:学员登录各自租户建三条规则并更新 grade profiles——先说给 15 分钟,再改口'10 分钟其实就够了'。

"Now, why we are doing this is so that when we hire somebody in the locations that we have created"— 这么做的目的:当我们在这些(所建的)地点雇人时,员工就能命中我们配好的区间。

46:15

Executive 规则多选

Executive 规则多选
  • 画面 Create Compensation Eligibility Rule「Cure Executive Eligibility」:Source External Field =「Management Level (Compensation)」、操作符 any in the selection list、Comparison Type「Value specified in this filter」,右侧候选列表展开。
  • 候选列表混合多套编号体系(1 Board of Directors、1 Executive Vice President、1 Vice President、2 Board of Directors、2 Chief Executive Officer、2 Executive Vice President、2 Individual Contributor、3 Executive Vice President、3 Vice President、4.1 Manager、4 Director…)——delivered 与自建 management level 并存的直观证据。
  • 讲师熟练示范:因为建过多次、熟悉字段所以快——'这就是你们要练到的程度,但请别急着求快'。
  • 勾选结果(口播):2(chief executive officer)、3(vice president)、5(director),并自评'选 2 似乎不对,但不影响我们方向'——最终以 00:47:30 的 View 页为准。

"I'm going to give it the name QR executive eligibility. My value will be management level compensation."— 我把它命名为(Cure)executive eligibility,值用 management level (compensation)。(口播 QR/Q 为租户前缀 Cure 的字幕误识)

47:30

作业澄清与预告

作业澄清与预告
  • 画面 View Compensation Rule「Cure Executive Eligibility」:Derived Logic「Management Level (Compensation) any in the selection list 2 Chief Executive Officer, 3 Vice President, 5 Director」;Rule Conditions 1 item:And / Management Level (Compensation) / any in the selection list / 2 Chief Executive Officer、3 Vice President、5 Director。
  • (含 00:44:30 合并)作业一(exploratory assignment):自建一条 company=Cure Private Limited(各学员用自己租户里的公司)+ time type=full time 的 eligibility rule,下节课配 salary plans 和 car allowances 时用。
  • 学员澄清:不是把 executive 规则改成 company+time type+management level 三条件——company+time type 必须是独立新规则,现在不挂到任何地方,下节课才用。
  • 作业二:照屏幕复刻这条 executive eligibility rule,再建一个'完全相反'的(non-executive)——先建出原版才好取反。
  • 下课预告:下节课完成整体 compensation 并做测试(testing);此帧也是 executive 规则最终形态的画面证据。

"You have to create one eligibility rule, which only includes your company and time type."— 你要单建一条只含 company 和 time type 的 eligibility rule。