The document summarizes the new message delegation feature and other updates in release 4.02 of the microblogging software. The message delegation feature allows companies to delegate message creation and approval across different social media accounts or "voices". It creates separate message instances that can be approved and published independently for each voice. Other new features include the ability for super admins to create branded applications for white label clients and fixes to unread counts, authorization issues, and group analytics errors.

1. 4.02 Release Notes
Release Date: February 3, 2012 Anticipated Downtime: None
New Features
Message Delegation
NOTE Feature Availability
The message delegation feature is not yet generally available; it will be enabled
in the Admin panel on a per-customer basis.
The message delegation feature allows a company to use a “hub and spoke”
model for microblog message creation and publishing, instead of the default “cen-
tralized” model. It affects both message creation and approval path functionality.
In the default state (off, or the “centralized” model), a single instance of a micro-
blog message is created, follows the approval paths configured for the voices
associated with it, and must receive approval from all associated voices in order to
be published through any of the voices.
For example: a message is to be posted on Facebook through Voice A, and
posted to a different Facebook account through Voice B. A member of the
approval team for Voice A approves the message, but a member of the approval
team for Voice B rejects it. The message cannot be posted through Voice A until it
has received approval from Voice B.
When enabled (turned on, or the “hub and spoke” model), multiple instances (cop-
ies) of a message are created, one for each voice, and the message must receive
approval only from the approval teams associated with that individual voice before
being published. The instance of the message can be published as it was written,
edited, or rejected regardless of what action is taken on the other instances of the
message within the other voices.
For example, a message is to be posted on Facebook through Voice A and posted
to a different Facebook account through Voice B. Upon creation, separate
instances of the message are created; one for Voice A and one for Voice B. The
approval team for Voice A approves the message as written, and it published
according to schedule. A member of the approval team for Voice B makes
changes to the message and resubmits it for approval. The edited message fol-
lows the approval path associated with Voice B, and is posted on schedule.
4.02 Release Notes January 31, 2012 1

2. Important Fixes
TIP Assigning Messages in Hub and Spoke Model
When using the hub and spoke model, the user creating the messages will likely
want to leave the source (original) message unassigned (that is, assigned to
himself by default) until all of the voices are selected and the multiple instances
of the message are created. That way, each instance of a message can be
assigned to the appropriate writer (or manager, who can then reassign it to the
appropriate writer).
When the message delegation feature is turned on, the “repeat” function on the
message is applied to the original “source” message—not the separate instances
of the message. Each “repeat” of the original source message is copied into a
separate instance for each voice.
Each instance of the message is tracked as a separate event in the system; it
receives its own message detail page and appears independently in the All Activ-
ity and Recent Engagement streams. Message versioning is disabled when Mes-
sage Delegation is turned on.
Branded Application Creation for White Labels
A new “Super Admin” role (only for designated, trusted users within white label
companies) has been created, and given the ability to create branded applications
for Facebook and Twitter within the system.
Important Fixes
The following were fixed as part of 4.02
Table 1-1 4.02 Fixes
JIRA Description
DEV-8922 Corrections to Unread Item Count in Initiative Inbox.
DEV-9145 “Target this version” button still enabled when user has been
de-authorized.
DEV-1952 Under certain circumstances the Group Analytics page would
not launch correctly, and would display a “missing campaign
group id” error.
2 January 31, 2012 4.02 Release Notes