@Jacob-DDdev We appear to be using the term "support" and "available"
slightly differently. API access for processing rules is not officially
supported in any version of the Analytics APIs (1.3/1.4/2.0). The
version of GetProcessingRules that some have used in the past is an
internal Adobe API that was unintentionally exposed a few years back but
never officially documented or released, thus it's not supported nor
officially available. The undocumented and internal GetProcessingRules
To answer @anmassey's question, there is no announced timeline for
end-of-life with API 1.4. RSiteCatalyst is not provided or supported by
Adobe but is an open-source project supported by a community of users.
Saumya's suggestion will work if you want to go that route. From a
product perspective, we are unlikely to add support for more than 200
items in a dropdown filter as scrolling through 200+ items in a drop
list is not a great experience for most users.
Cohort reports are only available in the Analysis Workspace UI but there
is not a specific "cohort report API" method that Analysis Workspace
calls. Instead, Analysis Workspace uses a combination of fancy segments
and multiple data requests to construct the cohort panel. You can
produce a cohort panel by using API 2.0 and constructing the segments
and data requests for the inclusion and return similar to how Analysis
Workspace does it. I recommend you use the Workspace debugger to analyze
API support for Processing Rules is not available in API 1.4 or 2.0 at
this time, including read-only API methods. Processing Rule changes are
currently restricted to the user interface. There is no announced
timeline for when this functionality will be available by API.
Processing Rules API is not available in 1.4 or 2.0 at this time,
including read -only API methods. Processing Rule changes are currently
restricted to the user interface. There is no announced timeline for
when this functionality will be available by API.
That's a possibility. We'll need to consider how such a change would
impact functionality in the UI such as sharing and schedule recipients,
etc. Because Analysis Workspace is built on the 2.0 API set we generally
want to keep behaviors in the API consistent with behaviors in the UI. i
appreciate the feedback in this thread.
Note that non-admin users can see all users in the company, including
First Name, Last name, and Email address, when they take actions in the
UI such as sharing segments and Workspace projects, adding recipients to
alerts and scheduled reports, etc.The three elements of admin status,
title, and phone haven't been previously exposed in the UI so that is
additional information that was added for API 2.0. We can consider
making a change such that only admins can pull the lists of users via
API but ...