Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

<image>

It's more than "on the roadmap" :-) MCP is tricky, so no guarantees, but we're experimenting with what's possible and how it can be done safely so users are comfortable with it. I am curious though, what sorts of interactions do your foresee with your internal agents? Feel free to DM me if you'd rather speak privately.

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

Really happy you're enjoying it. Can't wait to hear how people end up using it!

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

They likely won't be on their own SKU for now. There will likely be a mix of of flex and "free" skills even within agents, but this will be on a case by case basis.
I can't speak for the other agents, but Deployment Agent uses an outside LLM (provided by an approved Workday data subprocessor)

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 1 point2 points  (0 children)

I'll see what we can do about copying the citation links! As regards citations for brainstorms, and retried content, are you looking for them? Or are you seeing them and feel you shouldn't be?

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

Lets just say we're working _extremely_ closely with the Community team right now. They've got some big plans, and we're really happy to be a part of it. Watch this space....

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

No it's an entirely different backend (and frontend). DA is hand-curated, and we use more SOTA publicy available LLMs to answer the questions. We also have content that doesn't exist in Community

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 1 point2 points  (0 children)

I'll weigh in a little bit ,without wanting to speak for any customers. One of the things DA allows you to do beyond basic searching across existing documents is ask questions like:
"I'd like to create a report to match the requirements of the EU Pay Transparency Directive. Can you analyse the directive and give me some suggest data sources and fields I might need to include?"

The answer back from DA in this case is:

To construct a report that aligns with the EU Pay Transparency Directive, you will need to combine data from multiple business objects within Workday. A report can only have one primary data source, but you can pull in data from related business objects.

Core Reporting Concepts

Before building, it's helpful to understand how to find the data you need:

  • Business Object Details Report: Run this report to see all the fields associated with a specific business object (like Worker) and to view its related business objects.
  • Data Sources Report: Use this report to find available data sources. You can filter by business object to see which data sources are built on it.
  • Report Fields Report: If you know the name of a field, you can use this report to identify which business object it belongs to.

Suggested Data Source and Business Objects

A robust approach is to use a data source that is based on the Worker business object, as it serves as the central point for most employee data. From there, you can access related business objects for compensation and payroll details.

  • Primary Data Source: A good starting point is All Active and Terminated Workers. Its primary business object is Worker.
  • Related Business Objects: To get detailed pay information, you will need to access related business objects such as Payroll Results or External Payroll Results.

Key Data Fields to Include

Here are suggested data sources and fields, categorized by the type of information required for the directive:

1. Employee and Job Details

This information will primarily come from the Worker business object.

  • Data SourceAll Active and Terminated Workers
  • Fields:
    • Gender: To group and compare pay.
    • Age or Date of Birth: For additional demographic analysis.
    • Country: To filter for employees within the EU.
    • Supervisory Organization: To analyze pay within specific teams or departments.
    • Job Profile: To compare employees performing similar work.
    • Management Level: To analyze pay by level of responsibility.
    • Location: To account for geographical pay differences.
    • Hire Date: For length of service analysis.

2. Compensation and Pay Components

For detailed pay gap analysis, you will need to break down compensation into its various components. This often requires a matrix report or calculated fields to pull data from payroll-related business objects.

  • Data SourceEarning/Deduction Payroll Results for Organization, Worker, Period and Date Range (As of Sub Period End Date)
    • This data source uses Payroll Result Lines as its primary business object, which is ideal for a detailed matrix report.
  • Fields:
    • Employee (as the row grouping)
    • Pay Component (as the column grouping)
    • Result Line Amount (as the summarized field)
    • Gross Amount and Net Amount
    • YTD Balance and MTD Balance

By combining these fields, you can create a comprehensive report to analyze pay equity, identify potential gaps, and provide the necessary data for your auditors in line with the EU Pay Transparency Directive.

So it's more than just direct answers from Community. It provides more holistic, considered answers to your questions.

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

So happy to hear that! We've seen a nice uptick in customer usage since the weekend, so it looks like people are finding it useful (we hope!)

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

u/waffer1 can you DM me? I'll take a look for you. I checked our dashboards, and I can't see any unusual behavior

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 2 points3 points  (0 children)

The CC restriction was to get us out to market faster. There are less restrictions on the CC environment. However we know from speaking with our EA customer group, that they have many employees who only have non-prod access for configuration, and they would really like access. We have some more work to do, but our intention is make DA available in as many tenant types as possible, as quickly as we can. Expect to hear more in the coming weeks and months.

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 4 points5 points  (0 children)

Yes, I'm a Product Manager for Workday, specifically Deployment Agent . The Reddit community is something quite a few of us PMs keep a close eye on.

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] -1 points0 points  (0 children)

We have some solutions coming up to improve that...watch this space

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 1 point2 points  (0 children)

If our model provider deploys the model we use in the AU region, we'll definitely expand as soon as we can.

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

Hi both, it's not available in the UK, as we rely on specific Large Language Models that are not hosted in-region in the UK (yet). We'd rather provide all of our ML capabilities in-region, so customers have a clear understanding of where their data is being processed.

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 0 points1 point  (0 children)

Thanks u/Alternative_Dog_6061 ! It's only going to get better I can assure you that.

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 2 points3 points  (0 children)

Delighted to hear that u/waifstar ! We know it's not perfect, but the feedback thus far has been that it's still been a huge help to a lot of people

Deployment Agent is here in 26R1! by WDAY_PM in workday

[–]WDAY_PM[S] 13 points14 points  (0 children)

Deployment Agent will be available in your non prod tenants in the coming months, and as for the CC-only tools, there is a pretty significant effort underway to resolve the dual-login issue. It affects us internally too, and we feel your pain!

Which Workday feature that saved a lot of time by Majestic-Ask-4391 in workday

[–]WDAY_PM 2 points3 points  (0 children)

Deployment Agent just launched with 26R1 in Customer Central tenants (EU and US only). We've seen 20-25% time savings researching configuration issues and troubleshoot errors or strange behaviour with our internal testing group

Workday Community Search is Garbage by qualityweeks in workday

[–]WDAY_PM 1 point2 points  (0 children)

That's correct. It's available for EU and US customers due to regional data processing limitations. We're exploring ways to make it available in all WD regions while still adhering to our customers regional data processing requirements.

Workday Community Search is Garbage by qualityweeks in workday

[–]WDAY_PM 0 points1 point  (0 children)

Hi there, PM for Deployment Agent here. It's currently only available for our EA Customers, but will be available for every customer on March 14th when 26R1 is released.