Dev Roles Seeing Excessive Activities in Automation Section of Workflow Studio and Creator StudioDescriptionThe problem looks to be due to the following:In the Washington D.C. release, Process Automation Designer is using the GlideRecord GraphQL API to query the sys_pd_process_type record. This API enforces ACLs automatically. This is why the the activity-picker macroponent reference is null (it is a referenced value on a table they do not have permission to read).In Xanadu, the API uses GlideRecord to query sys_pd_process_type, rather than GlideRecordSecure. The Xanadu release contains the fix for this issue. Upgrading should resolve this issue.Steps to Reproduce Login to instance 2. Impersonate CD.TEST (User has delegated developer role)3. Navigate to Creator Studio4. Open the creator app test and open automation section5. Try to add an activity and observe that other activities can also be seen in Creator StudioWorkaroundThere are two workaround options that may be applied: Grant the user(s) the ui_builder_admin role or Add a delegated_developer read ACL to the sys_ux_macroponent tableRelated Problem: PRB1847488