Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Workday-Pro-Integrations Exam - Topic 2 Question 16 Discussion

You are configuring an EIB that uses a custom report as its data source. When attempting to transfer ownership of the report to the Integration System User (ISU), the ISU does not appear as an option for new report owners. You confirm that the ISU already has the necessary access to the report data source and related fields.Within the Custom Report Creation domain, which security configuration should you update to allow the ISU to appear as a valid report owner?
A) Assign the ISSG to a row within the Report/Task Permissions table that has Modify access enabled.
B) Assign the ISSG to a row within the Integration Permissions table that has Get access enabled.
C) Assign the ISSG to a row within the Report/Task Permissions table that has View access enabled.
D) Assign the ISSG to a row within the Integration Permissions table that has Put access enabled.

Workday-Pro-Integrations Exam - Topic 2 Question 16 Discussion

Actual exam question for Workday's Workday-Pro-Integrations exam
Question #: 16
Topic #: 2
[All Workday-Pro-Integrations Questions]

You are configuring an EIB that uses a custom report as its data source. When attempting to transfer ownership of the report to the Integration System User (ISU), the ISU does not appear as an option for new report owners. You confirm that the ISU already has the necessary access to the report data source and related fields.

Within the Custom Report Creation domain, which security configuration should you update to allow the ISU to appear as a valid report owner?

Show Suggested Answer Hide Answer
Suggested Answer: A

In Workday, for an Integration System User (ISU) to be selectable as a Custom Report Owner, the security group the ISU belongs to must have Modify access to custom reports.

From Workday's security configuration principle:

An ISU does not appear as a valid report owner unless its security group has Modify permission in the Report/Task Permissions section of the Custom Report Creation domain security policy.

This is because report ownership requires writelevel access over custom report objects.

Therefore, you must update the Report/Task Permissions table to include the ISSG with Modify access.

Options B, C, and D are incorrect because View or Get/Put do not provide report ownership capabilities.


Contribute your Thoughts:

0/2000 characters
Maia
1 day ago
This is confusing, can someone explain why A is better than D?
upvoted 0 times
...
Golda
6 days ago
I thought it was all about Get access, but A makes sense too.
upvoted 0 times
...
Mica
11 days ago
Wait, why would you need Modify access just to transfer ownership?
upvoted 0 times
...
Laurena
17 days ago
Definitely agree, A seems like the right choice!
upvoted 0 times
...
Selene
22 days ago
I think you need to go with option A for Modify access.
upvoted 0 times
...
Gilberto
27 days ago
I thought View access was just for seeing reports, not for ownership. I think we need to focus on Modify access instead.
upvoted 0 times
...
Vilma
1 month ago
I feel like we discussed that Put access might be necessary for certain integrations, but I don't know if it applies here.
upvoted 0 times
...
Kiley
1 month ago
I remember a practice question where we had to assign permissions, but I can't recall if Get access is sufficient for ownership transfer.
upvoted 0 times
...
Aron
1 month ago
I think we might need to give the ISSG Modify access in the Report/Task Permissions table, but I'm not entirely sure if that's the right approach.
upvoted 0 times
...

Save Cancel