Release Notes: Engage
ENGAGE 2.4 Release Notes
ENGAGE 2.3 Release Notes
SPROUT ENGAGE 2.4 Release
OVERVIEW
- Publisher
- Publish Flow Improvements
- Pointroll Platform reporting improvements
- Added Dynamic Action Triggers
- Added tokens from Facebook APIs
- Component Asset Manager
- Performance Optimization
NEW FEATURES
| Enabled the uploading of SVG or SVG URLs into the asset manager | You may now upload .svg files directly to the asset manager. A thumbnail is automatically generated. The svg asset may then be dropped into any project and manipulated like any sprout asset. | |||
| Added a PointRoll Platform (reporting only) | Added Event Tracking interface to Pointroll backend. | |||
| Allow Publish to Stream to send to one or more users/ friends | Facebook campaigns can now allow end-users to share sprouts directly to their friends’ walls without leaving the Engagement App. Previously, users could only post to their own walls. | |||
| Added an “enter full screen mode” option for Control Media action | Control Media action can now be used to activate full screen mode for the Video Component. We’d like to allow designers to show a button that can open a video in full screen mode.* If the video is not currently playing, it will start playing and enter full screen mode
* If the video is currently playing, it will continue playing in full screen mode |
|||
| Dynamic Action Triggers added for slideshow component | Dynamic action triggers are now available for the slideshowComponent. this includes “play”, “pause”, “stop”, “next”, “prev”, “playback complete”. | |||
| Add an enable/disable Facebook Publisher Share button action so designers can have more control | Now designers have to explicitly enable/disable the Facebook Publisher Share button, but this gives much more control over when it’s appropriate to Share. Most of the time designers should add a FB: Publisher Sharing action to enable the share button on the Editing Canvas’ “Sprout published” trigger. | |||
| Add a new asset provider for .xml files so we can upload XML snippets for designers to use | You may now upload sprout elements directly to the asset manager. Sprout elements must have a .xml file extension. A sprout element is any sprout XML snippet, including a single element, group of elements, a page or even an entire sprout. Once in the asset manager, sprout elements may be dropped into any project.Anyone with access to the debug panel can now save any sprout element directly to their local machine. Open the debug panel and select the tab corresponding to the part of the sprout you wish to save: “Application”, “Current Page” or “Selected Elements”. Click download and you will be prompted to save a file called “sproutsnippet.xml”. This will be a copy of the same XML you see in the currently open tab. This XML may then be added to the asset tray for any builder project. | |||
| Way to store persistent arbitrary session data for Facebook users | Facebook Component now has two new actions and one new dynamic property (token):Actions:
- Set Preferences: Allows designers to store persistent cookie data per-campaign which can be displayed via the below token via {fb.prefs.prefName} where “fb” is the name of your Facebook Component and “prefName” is the name of the preference you put in. - Clear Preferences: Designers can also clear specific data out of the user’s cookies with this action. Token: - A new token “prefs” which can be used by {fb.prefs.someKeyName}. Info has been added to https://dev.sproutbuilder.com/confluence/display/product/Facebook+Feature+Overview#FacebookFeatureOverview-Tokens |
|||
| Some way to be able to “set” some property to a bindable token (useful for async tokens) | You may now use the set property action to bind a element property to a token, as opposed to doing a one time translation.For example, setting a text elements plain text property to {someText} will set that text areas text to the value of {SomeText} at the time the action is run, one time only.
Setting a text elements plain text property to {someText} will bind that text area’s text property to {someText}, such that it will change any time {someText} changes. |
|||
| Tokens to pull Facebook profile data such as birthday, marital status, etc. | Designers can use a variety of tokens to pull our information about a current user’s profile or the current user’s friends’ profiles. The syntax is {fb.user.} or {fb.friends.} depending on whether you’re interested in the current user’s data or his/her friends’. For example, to get the current user’s first name, a designer can type {fb.user.firstName}. To get a random TV show that the user likes use {fb.user.tv|maxItems=1|random}. You can also get info about the user’s friends, like {fb.friends.firstName|maxItems=3} would print a comma-delimited list of 3 of your friends’ first names. | |||
| Allow overriding of the default mixer sprout | Designers can now specify an overridden mixer sprout ID for engagement applications that have more than one mixer sprout. For example, if you want to launch a campaign that has a full-size engagement app on your homepage as well as a smaller FB Publisher app, you can accomplish this by having two mixer sprouts in your campaign. | |||
| Component based asset manager for Mixer | Create the actions, tokens and components required to implement the asset panel in the mixer. Button component now support set property->text or htmltext to alter its label | |||
| Use gallery component to display pages panel in mixer | The sprout gallery component can now display page thumbnails from either the sprout being edited or the sprout being played. This allows the gallery to act as a pages panel in a mixer sprout or a thumbnail menu in any sprout. | |||
IMPROVEMENTS
| Added limit parameters to the gallery component | The gallery component now supports a property called “Max items”. Setting this value to anything greater to zero will limit the number of items displayed in the corresponding gallery to no more than that value. |
| Move marketing content on sproutbuilder.com to sproutinc.com | The homepage of sproutbuilder.com will now forward to sproutinc.com. There will be buttons to signup and login from sproutnc.com, which will forward back to sproutbuilder.com. |
| Add a “Publish completed” dynamic trigger to the Editor Canvas component (or application-level) | The Publish action now no longer has any properties specifying what ‘Form Page’ ‘Interstitial Page’ etc to use – now it just publishes, and the mixer designer needs to add explicit goToPage actions on the Publish button and the Publish Complete trigger. |
| Don’t prompt FB Connect login box until a FB-specific action is triggered | For Facebook-enabled campaigns, now the Facebook Connect login dialog is no longer shown upon loading of an Engagement Application, but rather shown on-demand, only when a user interacts with a Facebook-enabled portion of your campaign. |
| builder/player should load synchronously, engagement with preloader asynchronously | When a preloader is spec’d in Mixers as Mixer_preloader, we’ll run asynchronously for a smoother preloader experience, at a slight cost to startup speed. |
FIXED BUGS
| Account admin page displays one account as multiple records, one for each PayPal subscription | Improved user interface for the “account” admin tab |
| Custom tab creation for Facebook Applications | Designers can emulate Facebook tabs or whatever custom they’d like above their Engagement Apps to create FB Canvas Apps that are more tightly integrated with Fan Pages. List of allowed HTML tags on Canvas Pages: http://wiki.developers.facebook.com/index.php/Allowed_FBML_and_HTML_Tags#Canvas_Pages:_Allowed_Tags |
| Set property on tokens in XML when mixer loads a derivative sprout for editing | You may now re-edit wizard type mixers. If you use text inputs or other interactive components to set values in a sprout, user inputted values will be restored to these fields when a user re-edits their sprout. This feature allows designers to create mixer style campaigns that the user can re-edit without losing the values that they originally input into the wizard. |
SPROUT ENGAGE 2.3 Release
2.3 – Engage
Bugs
XML compression on S3
Improvement/Tasks
Add support for more animation easing types
Don’t prompt FB Connect login box until a FB-specific action is triggered
Make asset panel Facebook tabs’ visibility more granular
Video Component needs set property->source/token support
New Features
Show Facebook Fan Box action
Check box for restricting aspect ratio
Deprecate sproutmixer.com
Generic gallery component
Initial Facebook Publisher exploration and work
Go-to-Page action improvements
Create Dynamic Triggers
Engage 2.3
Bugs
XML compression on S3 We use HTTP compression to speed up data retrieval in live sprouts created via engagement campaigns.
Improvements
Add support for more animation easing types Added new animation easing types – “back”, “bounce”, and “elastic”.
Don’t prompt FB Connect login box until a FB-specific action is triggered For Facebook-enabled campaigns, now the Facebook Connect login dialog is no longer shown upon loading of an Engagement Application, but rather shown on-demand, only when a user interacts with a Facebook-enabled portion of your campaign.
Make asset panel Facebook tabs’ visibility more granular The meta asset panel component now has three new options. You may turn on or off each of the Facebook tabs separately.
Video Component needs set property->source/token support You may now use the set property action to set the “source” attribute of a video. Additionally, {tokens} are supported in the media dialog.
New Features
Show Facebook Fan Box action A new Facebook: Show Fan Box action is available in F3-enabled engagement applications allowing end-users to easily become fans both inside native Facebook applications and in the wild with Facebook Connect all without leaving the engagement experience.
Check box for restricting aspect ratio F3 campaigns can now harness the power of Facebook events. Users can create Facebook events and RSVP to an existing event all from within Sprout Engage.
Deprecate sproutmixer.com Sproutmixer.com will now be deprecated
• All campaigns will now appear on sproutbuilder.com
• All campaign users are now treated as anonymous users by our backend system
• Improved performance and lowered database overhead with improved security by our system
A different session cookie is now used for each mixer and the builder.
• This allows users to have a session open for as many mixers as they like and one for the builder. The system will treat them separately and will not kill the previous session that was open as it was before.
Generic gallery component Please note the following new default values in the Gallery Component:
• The default size of the component is now 290 x 180
• The default caption size is now 175 x 75
• The default margin in now 6
• The default selection color is now #e4e4e4
• The default selection border color is now #cccccc
• The default selection corner radio is now 5
• The default fill type is now SOLID
Other Important Updates in the Gallery Component:
• Images now display wait indicators as they load
• The drawing of rounded corners on borders has been improved
• You may now use a cell padding of -1, this will cause cells with a border of 1 pixel to not exhibit a 2 pixel border between cells
• If the cell padding is less than or equal to zero, the image thumbnail border color will change to the selected border color when that cell is selected
• Text is no longer cut off midway. If there is not enough height to display a line of text, that text will not be displayed
• You may use the Twitter component as a source. If you have a twitter component on the stage named twitter, you may use {twitter.feed} as the source of the gallery component. This will display all of the available tweets and profile images from the current search in the twitter component.
• The gallery component has a trigger available called “Selection Changed” that is fired whenever someone selects or de-selects and item in the gallery
• The gallery will display any RSS feed. If the feed does not contain thumbnail images in the media RSS format, it will look for the first image in the description
• The gallery now correctly works with Sprout’s EAPI feed used with the campaign console. Now designers can create custom galleries for campaigns. The URL for this feed is http://jelly.sproutinc.com/eapi/campaign/sprouts/(campaignID) where campaign ID is the ID of the sprout campaign you wish to display sprouts from.
• The selection border is now displayed in the cell padding area. If there is not enough cell padding, the selection border will be clipped
• The gallery feed does not load until the page it is on becomes visible
• You can now use the “set property” action set the source of the gallery
The following properties can be used in tokens that reference a gallery:
1. title: the title of the last selected item
2. description: the description of the last selected item
3. thumbnail: the URL of the thumbnail of the last selected item
4. selected_ids: a comma separated list of the IDs of all items selected in the list, uses the guid field in the RSS field for a value.
5. all_ids: a comma separated list of the IDs of all items in the gallery, uses the guid field in the RSS field for a value
Initial Facebook Publisher exploration Sprout Engage can now be integrated into the Facebook Publisher on a brand’s Fan Page as well as a user’s news feed and stream. This allows brands to easily engage their users directly in the Fan Page experience.
Go to page action improvements The Go To Page Action now has new properties that match functionality with Links & Tracking. It now supports opening the first/last page of a sprout, next/previous page of a sprout, and going to a page specified by its name.
Create Dynamic Triggers Create dynamic triggers:
- Twitter: On new tweet
- Gallery: On Click, On Selected Items
Changed triggers are described in the release note for each component.
https://dev.sproutbuilder.com/confluence/display/product/Release+Notes
