Read time:ย 5 minutes

Last week, we made an honest case for custom objects.

Are they always the cleanest, most cutting edge way to capture non-delivered data within your Workday tenant? No. But can they get the job done fairly well for no extra cost? Absolutely!

If you missed last weekโ€™s strategy sesh, we highly recommend you check it out here before reading todayโ€™s newsletter.

Today, weโ€™re sharing more on the mechanics of custom objectsโ€”a step-by-step on initial configuration.

So, grab your coffee, tea, lunch, or snack (depending on where you are in the world ๐Ÿ˜†), and letโ€™s dive into todayโ€™s technical guideโ€ฆ

The basics of custom object setup ๐Ÿ› ๏ธ

If youโ€™ve never built custom objects yourself, the following walkthrough should give you a solid understanding of setup.

Today, weโ€™ll create a non-effective dated custom object that lives on the Job Profile business object (BO). The goal is to capture two additional categorizations that arenโ€™t WD-delivered:

  • High Market Visibility - Marks whether a role is public-facing or brand-sensitive.

  • Internal Career Track - Tags the roleโ€™s path within your internal career framework.

Letโ€™s do it! ๐Ÿ’ƒ๐Ÿป

This is where the good stuff lives.

Free builds awareness. Premium fills all the gaps ๐Ÿฆ„

Plus everything else in Premium:

โญ๏ธ Release Ratings & Reviews
๐Ÿ” Full archive access
๐Ÿ—ณ๏ธ A say in what gets built

Reply

Avatar

or to participate

Keep Reading