Automations is a powerful new tool that allows you to establish a ruleset and create a checklist of modifications that should apply to those assets on the first save or on every save.

Note that there is a specific user permission needed in order to use this new tool. Users in the "Administrators" group may receive permission to use the tool automatically, but other groups will need have this permission added to their user account group if they will be allowed to access this feature.

Get started

Find Editorial / Assets -> Application settings -> Automations.

Automations accordion menu

Then, create a new Automation.

New Automation.

Choose one or more criteria which will be required before any transformations occur.

Automation criteria

Once a user has set up their criteria rules, they can be viewed in the main asset in plain English, to help you troubleshoot.

Next, transformations will need to be created. Here are the available transformation types:

Transformations

Best Practices

  • This is considered a "destructive" process (data can be replaced or lost) and should be used with caution. Consider limiting the tool to only a handful of site admins with user group permissions.
  • Be as specific as possible. In most cases you'll want to specify a specific asset type or types so that a rules doesn't apply to all asset types. 
  • Setting the automation to apply on "first save" only means that a user could remove the transformation if needed. (I.e. you have an automation that is adding a #sports keyword tag to all articles in the Sports section. But, maybe there is an edge case where you don't want to have this one article with that flag. If the transformation is applied to every save, there would be no way to undo it.)
  • Test your automations by add a #test keyword criteria to your automation at first. Then, create a new article with a keyword of test and see if the automation works on the first save. If it works, you can then remove the #test criteria and make it more widely available.
  • Criteria can also be inverted, so that items with that content item are NOT included.
Inverted

Some criteria have more sophisticated implementations.

Some criteria have more sophisticated UI such as start time
Transformation body field

Examples

Here are some examples of how this can be used:

Your General Manager asks that all local videos in the Sports and News sections now have a headline which starts with "WATCH NOW:" in order to be more eye catching.

  • Criteria: 
    • Asset type: Video
    • Section(s): Sports, News
  • Transformation: 
    • Title field
      • Operation: Add value at the beginning of the field
      • Transformation values: WATCH NOW:

A columnist, Jane Townsend, asks if you can add her name as a keyword to every column she writes. This will then be used with BLOX Notifier to automatically trigger a post to her Twitter account each time a new column is published.

  • Criteria:
    • Asset type: Article
    • Section: Editorial / Columnists
    • Byline: By Jane Townsend
  • Transformation:
    • Keyword tags:
      • Operation: Keep existing keyword(s), add the specified keyword(s) in addition
      • Transformation value: #jane_townsend

Note: The hashtag in front of the keyword means it will be hidden from the front end, but is still actionable in BLOX CMS.

Your SEO consultant recommends that all of your local news content be set with a schema.org microdata item type of "ReportageNewsArticle" which will help search bots recognize local content on your site.

  • Criteria:
    • Asset type: Article
    • Section: News / Local News
    • Flag (exclude): Wire (must NOT have this flag)
  • Transformation:
    • Type of work:
      • Operation: Add the specified "type of work" if there is no existing "type of work" currently defined
      • Transformation values: Reportage

Note: All criteria can be inverted to make it require the opposite criteria as stated, such as the article must NOT have the flag of "wire" to meet the criteria rules.