Single-Source

Choose a unique description to distinguish the component from potential other Kanban Boards o the view.

In this field, you specify the title of the Kanban Board.

In this field, you specify the source. It contains two values: Single-Source and Multi-Source.

This field is used in configuring the height of the Kanban Board lanes using CSS.

This field is used in configuring the width of the Kanban Board lanes using CSS.

Switching it on will hide the Kanban Board.

Switching this toggle on will add a refresh button on the Kanban Board. 

Selection of the record definition, that serves as a source for the cards.

The field's value will be displayed as the headline of each card.

Display ID or Prefix Display ID Field should be mapped here.

Modified Date Field should be mapped here.

Here you can choose from 2 values: Login ID, and ID. The value you choose here should depend on the type of value the assigned person field contains in your record. If the Login ID is stored in the field which contains the Assigned person, then "Login ID" should be chosen here and likewise, the ID option can be chosen.

Here you should map the field which holds the data for an assigned person.

Here you can choose from 2 values: ID, and Display ID. The value you choose here should depend on the type of value the assigned group field contains in your record. If the ID of the group is stored in the field which contains the Assigned Group then, the ID should be chosen here otherwise the Display ID option can be chosen.

Here you should map the field where Group ID is stored.

This field determines from where the Kanban Board extracts its lanes. There are 3 types;

• Selection Field: It can be used for all the use cases.
• Behaviour: It can be used for use cases related to root objects of Agility Suite.
• Flow set: It is used for use cases of BWF Cases and Tasks.

Applicable only for BWF use cases. It helps to determine the correct Flowset.

If the "Source" is Behavior or Flowset, then this field should contain the ID of the corresponding Flowset or Behavior, respectively. The information is used to extract the status lifecycles and generate the lanes. 

If Successor Indication is enabled, the Kanban Board visualizes which successors are possible for a certain item, when dragging it. This option is available for Behaviors and Flowsets.

A field can be chosen, out of all the fields of type "Selection" from the record definition. The options of that field will be displayed as lanes on the Kanban Board.

The values of the selection field that you do not want to show in the Kanban Board can be put here. The values need to be comma-separated.

E.g., if you do not want to display the status 'New' in the Kanban Board, you can add the value of 'New' (1000) to the list, which hides the lane and therefore all the instances with this status option.

You can specify in which lane the Lane Change Dialog should be displayed.

A potential use case is when the status reason has to be specified for items when they are moved to the lane "Closed". The selection of the status reason can be handled in the dialogue.

The record that is associated with the item and acts as a group needs to be selected here.

The ID field of the group record needs to be mapped here.

E.g., the Record ID field from the Support Group Record contains the Id of the group.

Map the field, that contains the Display Id of the group.

Map the field that contains the name of the group that should be displayed to the end-user on the Kanban Board.

• Record: This value should be chosen when there is a record definition, that stores the association between people and groups, e.g., the "Support Group People Assoc Join", a join record, that stores the relation between CTM:People and CTM:Support Group.
• Association: This value should be chosen when there is an association between the group record and the People record.

Only applicable when the Association Mode is "Record".

A record needs to be selected, that represents the relationship between people and the group record.

Only applicable when Association Mode is "Record" 

Map the field which stores the ID of a person.

E.g., "PeopleRecordID" stores the ID of the person in "Support Group People Assoc Join".

Only applicable when Association Mode is "Record" 

Map the field which stores the ID of the group.

E.g., "Support Group IS GUID" stores the ID of the person in "Support Group People Assoc Join".

Only applicable when Association Mode is "Association".

Choose an association between CTM:People and the group record.

This expression is applied to the entry record and allows to filter out items with certain properties. 

This expression is applied to the group filters the groups, that will be visible on the Kanban Board.

This filter expression is applied when loading the users, which can be used on the Kanban Board.

The value in this field is : "'4' !=\"NULL\"".

Note: Sometimes the field will display an error, this error can be ignored if the filter works as per your expectations.

Ids of the field can be added here in a comma-separated format. Fields added here will be available in the filter section of the Kanban Board, and items can be filtered based on these fields.

1

Text Field Filter

2

Selection Field Filter

3

Date Field Filter

This expression should contain a URL. The link must start with "https://" or "http://" and will be extended by the ID of the respective entity that as clicked. 

Instead of providing a static link, here, the "Setting Value" object contains the base URL which can be extended by a suitable substring("task/").

Here, you need to select the view that you want to open up when changing lanes.

The dialogue will only open up when you move an item on the lanes where you have configured 'Lane Change Dialog Lanes' in the Lane Configuration Section.

This field will determine the size of the dialogue. There are six possible values in this field, a value can be chosen according to requirement.

This field will determine where the dialogue will open up. There are three possible values for this field, a value can be chosen according to requirement.

Here you can specify the title of the blade. It will be displayed at the top of the dialogue when it opens up.

Here, you need to select the view that you want to open up, by clicking the pen/edit icon on the Kanban Board.

This field will determine the size of the dialogue. There are six possible values in this field, a value can be chosen according to requirement.

This field will determine where the dialogue will open up. There are three possible values for this field, a value can be chosen according to requirement.

Here you can specify the title of the dialogue box. It will be displayed at the top of the dialogue when it opens up. 

The selected process is triggered when a group is dragged from the chipbar onto an item. The process should be used to assign the group to that item.

The selected process is triggered when a person is dragged from the chipbar onto an item. The process should be used to assign the user to that item.

The selected process is triggered when you change the lane of an item. This process should be used to change the corresponding field, which is represented by the lane. 

Here you can specify after how many days you want to change the format of the modified date.

For example, The date threshold is set to 5, so for days the modified date will be like "Modified 4 days ago", after the 5th day it will start showing the modified date in the format specified below.

This date format is pre-configured however, it can be changed according to requirements.

Allows you to change the colour of the toolbar.

Allows you to change the text colour of the toolbar.

Allows you to change the colour of Lane.

Allows you to change the text colour of Lane.

Allows you to change the colour of the card.

Allows you to change the text colour of the card.

Allows you to change the colour of the successor indication in the Kanban Board.

In this field, you can choose from all the selection fields available in the record.

Setting this field allows you to distinguish items based on an attribute, e.g., the priority. Just looking at the items, allows you to distinguish their priority.