Communicator - Attribute choices

When content is published, it’s sent to and stored in a Message Feed attribute. If it’s an Audience Attribute, each person’s content has the potential to be unique and personalized. If it’s a Project Attribute then the content will be the same for everyone.

It’s possible for all Characters and all content to be sent to the same Attribute. This is shown in Figure 123. The Communicator takes all the content, regardless of Message Feed attribute, and distributes it to the right channel (or “desktop app” as shown on the Communicator homescreen).

It’s also possible, and sometimes desirable, to create several Message Feed attributes. The reasons you might want to do this are:

  • if you plan to empty the feed at any time and don’t want to remove ALL messages, only certain messages. To do this, you’d need to split your messages into those you expect to purge and those you don’t
  • to better manage the project. If you have a busy or complex project, tracing through a single Attribute to see all the messages can take time. Dividing the Communicator activity into several Attributes makes it faster to find messages of certain types of function.

The diagrams below show how the Communicator deals with different Message Feeds – you’ll see that they all get merged into a single feed and distributed as before.

If you have an Enterprise license or by special arrangement with us, you can also use the Custom channel type and the standard Communicator will be switched to a customized Communicator in which Custom feeds can be distributed to unique buttons.

 Using several Message Feed attributes organized by content type

Using several Message Feed attributes organized by purpose/function

Using Communicator with custom channels

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request