The following are methods for ManagedTopics. All methods are static.
32.0
No
public static ConnectApi.ManagedTopic createManagedTopic(String communityId, String recordId, ConnectApi.ManagedTopicType managedTopicType)
You can create up to 25 managed topics per managedTopicType.
Type: ConnectApi.ManagedTopic
Only community managers (users with the “Create and Set Up Communities” or “Manage Communities” permission) can create managed topics.
35.0
No
public static ConnectApi.ManagedTopic createManagedTopic(String communityId, String recordId, ConnectApi.ManagedTopicType managedTopicType, String parentId)
You can create up to 25 managed topics per 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.
Type: ConnectApi.ManagedTopic
Only community managers (users with the “Create and Set Up Communities” or “Manage Communities” permission) can create managed topics.
32.0
No
public static ConnectApi.ManagedTopic createManagedTopicByName(String communityId, String name, ConnectApi.ManagedTopicType managedTopicType)
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.
Type: ConnectApi.ManagedTopic
Only community managers (users with the “Create and Set Up Communities” or “Manage Communities” permission) can create managed topics.
35.0
No
public static ConnectApi.ManagedTopic createManagedTopicByName(String communityId, String name, ConnectApi.ManagedTopicType managedTopicType, String parentId)
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.
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.
Type: ConnectApi.ManagedTopic
Only community managers (users with the “Create and Set Up Communities” or “Manage Communities” permission) can create managed topics.
32.0
No
public static deleteManagedTopic(String communityId, String managedTopicId)
Type: Void
Only community managers (users with the “Create and Set Up Communities” or “Manage Communities” permission) can delete managed topics.
32.0
32.0
No
public static ConnectApi.ManagedTopic getManagedTopic(String communityId, String managedTopicId)
Type: ConnectApi.ManagedTopic
35.0
35.0
No
public static ConnectApi.ManagedTopic getManagedTopic(String communityId, String managedTopicId, Integer depth)
Type: ConnectApi.ManagedTopic
32.0
32.0
No
public static ConnectApi.ManagedTopicCollection getManagedTopics(String communityId)
32.0
32.0
No
public static ConnectApi.ManagedTopicCollection getManagedTopics(String communityId, ConnectApi.ManagedTopicType managedTopicType)
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.
35.0
35.0
No
public static ConnectApi.ManagedTopicCollection getManagedTopics(String communityId, ConnectApi.ManagedTopicType managedTopicType, Integer depth)
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.
35.0
35.0
No
public static ConnectApi.ManagedTopicCollection getManagedTopics(String communityId, ConnectApi.ManagedTopicType managedTopicType, String recordId, Integer depth)
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.
32.0
No
public static ConnectApi.ManagedTopicCollection reorderManagedTopics(String communityId, ConnectApi.ManagedTopicPositionCollectionInput managedTopicPositionCollection)
Only community managers (users with the “Create and Set Up Communities” or “Manage Communities” permission) can reorder managed topics.
If you don’t include all managed topics in the ConnectApi.ManagedTopicPositionCollectionInput, the managed topics are reordered by respecting the positions indicated in the ConnectApi.ManagedTopicPositionCollectionInput and then by pushing down any managed topics that aren’t included in the ConnectApi.ManagedTopicPositionCollectionInput to the next available position.
If you have these managed topics:
Managed Topic | Position |
---|---|
ManagedTopicA | 0 |
ManagedTopicB | 1 |
ManagedTopicC | 2 |
ManagedTopicD | 3 |
ManagedTopicE | 4 |
And you reorder managed topics by including this information in ConnectApi.ManagedTopicPositionCollectionInput:
Managed Topic | Position |
---|---|
ManagedTopicD | 0 |
ManagedTopicE | 2 |
The result is:
Managed Topic | Position |
---|---|
ManagedTopicD | 0 |
ManagedTopicA | 1 |
ManagedTopicE | 2 |
ManagedTopicB | 3 |
ManagedTopicC | 4 |