You can find the topic board settings page as a sub page to the topics page or by clicking on settings for the respective topic board on the boards page.
Access required: Full access to the topic board
This is what the topic board settings page could look like with all its menus closed.
The following topics will be described in this article:
Action menu
New topic
Click on the green plus button or click on the new topic action in the action menu to createa a new topic in the current topic board.
Access required: Read access to the current topic board.
Exchange topics
Click this button to exchange topics
New topic board
Click this button to make a new topic board.
History
Import history - See the topic import history of the project
Export history - See the topic export history of the project
Move history - See the topic move history of the project
Archive topic board
You can not delete an topic board in Catenda Hub Instead you can “archive” it so that it does not show anymore.
Links to topics in archived topic boards will not be visible in documents or objects.
Archived topic boards can be restored by going to the settings of the archived board on the boards page.
After restoring a board the links will be visible again.
Note: You can see the topics in an archived topic board by clicking on “topic boards”. At the bottom of that list you can select “View archived”.
Topic board information
Topic board name - Change the name of the topic board
Owner - See who made the topic board
Description
Short description that will only be seen here so you and others that are configuring the board know what it is used for.
Statuses and types
Lock statuses and types for BCF 1.0 compatibility
BCF 1.0 only supports 2 statuses ("Open" and "Closed") and 4 types ("Error", "Warning", "Info" and "Unknown"). It is not possible to modify statuses or types on topic boards where this option is selected.
Status
When you create a topic board you will have the following default statuses:
A status has a Name, Color, and Meta-status.
By default there are three statuses that have an open and two that have a closed meta-status.
Add status - Click the add status text at the bottom of the status list to add a new status.
Edit status
Upon editing a status you will notice that you can assign a third meta-status called Candidate.
Color - Change the color of the status.
Arrows
Change the order of a status by using the arrows to move it up or down the list.
The top status will be the default status when you make a new topic.
The order of the statuses will also be the order the statuses will appear in the dropdown list when changing the status of an topic.
Delete
You can also delete statuses here down to a minimum of 1 open and 1 closed status.
Meta-status
Meta-statuses give a general idea of where in the workflow the status of a topic is.
Open - Topics with this meta-status are shown by default when you open an topic board.
Closed - Topics with this meta-status are hidden by default when you open an topic board.
Note: You can configure who is allowed to change the status of a topic with an open meta-status to a status with a closed meta-status in the access control section.
Candidate
Topics with a candidate meta-status are also hidden by default
This status is supposed to be for Topics that are neither open nor closed.
The candidate meta-status is meant to be for letting people know an topic is not completely finished drafting yet so it is not open yet.
In the flow it is therefore meant to come before open.
However, people also use this status for topics that have fallen outside of the regular flow.
Like an topic that is not finished and therefore closed but just no longer relevant.
People do not want to see it in the list by default and therefore use this meta status.
The minimum amount of statuses is one open status and one closed status.
Type
When you create a topic board you will have the following default types:
Types are configured similarly to statuses except they do not have meta-statuses and you can delete up to a minimum of 1 type.
Custom Fields
In this menu you will be able to add and modify custom fields in this topic board.
Access required: Full access to the topic board
Custom fields can be configured on the custom fields page.
Access required: Project administrator
Add custom field
You can add a custom field by clicking on the green Add a custom field button.
After clicking on the button you will be able to select your custom field in the add a custom field dialogue.
Mark as required
Yes or no
If the custom field is set as required users will not be able to submit an topic without filling out this custom field.
Set default value
Default value for your custom field type
The default value is mandatory when the custom field is marked as required.
Remember to click add.
Modifying custom fields
By clicking on a custom field that has been added you will be able to configure its settings.
Mark as required
Yes or no
If the custom field is set as required users will not be able to submit an topic without filling out this custom field.
Set default value
Default value for your custom field type
The default value is mandatory when the custom field is marked as required.
Remove from topic board
Click the remove from topic board button to remove this custom field from the topic board.
Remember to click submit.
Access control
Users will be able to see an overview of what teams and users have which access to this topic board.
If all users have access to creating topic boards the lock will be green.
If access has been set for the creation of topic boards in project settings the lock will be orange.
Edit access
Click on "edit access" to configure access the access for this topic board.
You can read more about editing access here.
Access required: Full access to the topic board.
Unlinked fields
If an topic has been imported with statuses, assigned users or other settings that do not exist in this topic board the fields of these topics will be unlinked and the topics will not show up in the topic board until these fields are linked.
Link these fields to existing fields by specifying what existing field each unlinked field will be mapped to.
Access required: Administrator