Best practices for creating CDT

Hi Surjit,

In addition to the above suggestions, refer the following links:

https://community.appian.com/w/the-appian-playbook/967/an-introduction-to-query-optimization (CDT/Table Design Steps Section)

https://community.appian.com/w/the-appian-playbook/156/managing-reference-data

 

Thanks,

Hema

Thanks Hema. Where should we use Constant and where should we use Reference Data( as mentioned in the link you provided). I can use constant to store all state or LOB? Does it have any performance or resource utilisation benefit?

Regards,

Surjit

Thanks Hema. Where should we use Constant and where should we use Reference Data( as mentioned in the link you provided). I can use constant to store all state or LOB? Does it have any performance or resource utilisation benefit?

Regards,

Surjit

Hi Surjit,

AFAIK, for storing a list of values like Status, constants can be used. Also, the labels for components can be saved in constants. When there is collation of data, constants won't be of much help. In that case, Reference Table can be used.

For example, a list of all the Branches in Engineering in a certain university can be displayed using a constant. In the real time, every Branch has an HOD, a SPOC etc., In order to store all this data, a Reference or a Master Table will be of more help than a constant.

Hope this helps!!! 

 

Thanks,

Hema

A constant can be used to store all states or LOB values only if the names are needed. The active/inactive state of these values can't be stored in the same constant.

Thanks,
Hema