Subscription Name

Problem/Motivation

The name of the subscription is displayed using the machine name. As the machine name is, by definition, intended for internal use, it would be better to use the entity names or non-machine-names where the opportunity arises.

While it is great that the subscription name is automatically generated and specifically includes all the identifying parts in an unambiguous manner, in some cases, this is presented to end-users who are more than likely unaware of things like nodes and event types.

For example, I'd like the subscription to say "Subscribe to Blog Posts" rather than "Subscribe to content node-blog_entry - publish".

Proposed resolution

Tricky. Seems like a good candidate for a tokenized field to specify the subscription label name. By default, it would be what it is now, but have the option to override it with something simpler or different as needs arise. I don't know that a separate field is required for each combination - that seems a little messy. Rather, just a way to specify the format and let it sort it out for the specific variations if they are used. For example, if someone wants to have a "publish" and "unpublish" event, then they'd need to specify the {event type} as a token in the label. If they only have "publish" events, then they can leave out that token or add in the word "Publish" or choose a word or phrasing that they prefer.

User interface changes

On the content type configuration, perhaps an extra field could appear there, with the option to include tokens for the various components that are currently used in generating the subscription name as well as additional tokens like the content name. But with the option of overriding everything and just putting in a content-specific label that may get used for all subscription events.