This is a good idea. We will add this into our backlog and work on this as soon as we have an opportunity. For the moment, this is not prioritized.

Hello,We already have the "Community" link in our menu. Add a direct link is not relevent in this case, as ACS forum is accessible only after 1 click once your are in the Community page.

Hello,This is not doable and not in the roadmap. The only way to "extend" this is by adding a custom resource and create your own enumeration. In this case, the OOTB enumeration won't be used, but it can't be hidden.

Hello,This will be available in August release (ACS 19.3). You will be able to share a segment code and retrieve it into Dynamic Reportings. This will be doable via the workflow.

It works only if the link is a 0-1, not a 1-1 (in this case, all profile data won't be accessible by someone out of the org unit).

Adobe says this is in our backlog We want to manage proof with Profile data, which means we will access to all workflow environment.For this, we will use the notion of Address substitution, like we do in ACC. There is still no release date, but this is how we want to achieve this.For now, a workarou...

Like ACC, the question was on the number of recurring delivery in a workflow.

I know this is important, but there is no commitment for the moment.

Good idea!We will think about it. (CAMP-34598)

Hello,The count function is costly. Automate this is not our priority.Now, it's maybe possible to build a workflow for updating this value on a daily basis.