Before creating your custom screens, you may want to design custom fields to be used for your teams. It is recommended to do a thorough analysis of what fields are needed for your use case prior to running the Screen Designer. Once all necessary custom fields are decided upon, administrators can save time by adding these fields at once via TeamConnect Setup.
To use blocks for your custom pages, you must first create the necessary custom fields.
Custom fields can be created and displayed by category only. Because of this category dependency, you must carefully plan for which categories to create the desired custom fields, taking into consideration the following:
•For all categories and custom fields you add in an object definition, associated access rights are automatically created. They must be assigned to the appropriate users and user groups in order for the users to be able to view the categories and their custom fields.
•The root-level category in both custom and system objects is always automatically added to the object records to provide access to other categories (unless you do not intend to use categories and custom fields in your design at all). This means that all custom fields created for this category are automatically displayed in all records for all users.
•Always arrange your custom fields so that you do not have to replicate the same fields for different categories.
This improves performance and also prevents possible confusion if the custom fields of two categories are used in the same object record.
•A category name must be unique within its object if it has any custom fields included in Data Warehouse. For more information, see Data Warehouse Requirements for Custom Fields.