The system can automatically route objects being published to different destinations, based on the values of the objects' attributes.

Here is an example of automatic routing based on object categories.

Import this data file: http://forum.teradp.com/files/mimo/2012224232726_pubFilterByCat.xml

It defines two publishing destination templates - 'MustHaveCat' and 'FilterByCat'.

In the 'Destination' page in the administrative Web application create the root routing detination using the 'MustHaveCat' template:

Then create the sub-destinations - one for each category:

...setting the 'catName' parameter to the name of the associated category:

The result is something like this:

Now set the category of an object:

..and then publish it to the root routing destination:

The object will be publishing automatically to both the root routing destination ('/FilterByCat') and the sub-destination corresponding to the object category - '/FilterByCat/International' in this example.

The sub-destinations are not visible in the publishing dialog because they are filled with an automatic rules, so they cannot be selected directly by a user.

If an object has multiple categories it will be published in multiple sub-destinations.

Attempts to publish an object without categories result in an error (courtesy of the 'MustHaveCat' template):