Managed Topic Input

A managed topic.

Root XML tag

<managedTopic>

JSON example using recordId

This example creates a managed topic from an existing standard topic (using the recordId of the standard topic). It also creates a topic hierarchy by assigning a parent topic with the parentId.

1{
2"managedTopicType":"Navigational",
3"parentId": "0mtR000000001KLIAY",
4"recordId":"0TOD00000000cwk"
5}

JSON example using name

This example creates a new managed topic by name and creates a topic hierarchy by assigning a parent topic with the parentId.

1{
2"name":"Child Topic",
3"managedTopicType":"Navigational",
4"parentId":"0mtR000000001KLIAY"
5}

Properties

Name	Type	Description	Required or Optional	Available Version
`managedTopicType`	String	Type of managed topic. `Featured`—Topics that are featured, for example, on the community home page, but don’t provide overall navigation. `Navigational`—Topics that display in a navigational menu in the community. A topic can be associated with up to two managed topic types, so a topic can be both a `Featured` topic and a `Navigational` topic. You can create up to 25 managed topics per `managedTopicType`. To create a child managed topic, specify `Navigational` as the `managedTopicType` and specify a `parentId`.	Required	32.0
`name`	String	Name of the managed topic.	Required for new topics You must specify either `name` or `recordId`. You can’t specify both.	32.0
`parentId`	String	ID of the parent managed topic. If you specify a `parentId`, also specify `Navigational` as the `managedTopicType`. You can create up to three levels (parent, direct children, and their children) of managed topics and up to 10 children managed topics per managed topic.	Optional	35.0
`recordId`	String	ID of the record to become a managed topic. In version 32.0, `recordId` must be a topic ID.	Required for existing topics if the `Name` property isn’t used You must specify either `name` or `recordId`. You can’t specify both.	32.0

Chatter REST API Developer Guide

Managed Topic Input

See Also: