Component Configs

Owned by Content Writers
Last updated: Sept 23, 2024
2 min read

Attributes:

attributes.png
Attributes

The Attributes section offers a wide range of customization options for selected components, enabling users to tailor them to specific requirements. Users can modify selected components or fields, by using the attributes.

For example, users can adjust component or field sizes and apply custom CSS and SLDS classes for styling. Additionally, visibility and disability settings offer control over when and how a component appears on the page. These settings can be configured based on various conditions, providing dynamic UI customization.

The Attributes section is divided into several types, each catering to different aspects of component customization:

  • Basic: This includes basic options such as changing the label, assigning a model to component. The available options change based on the selected component or field.

  • UI: This includes UI options such as changing component size, adding padding as well as margin at specified locations, applying SLDS classes as well as custom CSS classes to the component, defining the layout type i.e., either grid type of flow type.

  • Visibility: This feature allows you to control the visibility of components.

  • Read Only: This feature allows you to set components as read-only.

  • Disability: This feature allows you to disable components.

  • Component: This feature allows you to set custom label names for components.

These features allow for complete customization of each component, enhancing both the design and functionality of the application.

Events:

Events.png
Events

In noKodr, Events define the triggering actions for automation created by workflows. They determine when a specific workflow should be executed based on user interactions or changes in the application.

For example, suppose you need to validate an email address entered in a field. You can create a workflow to check whether the email is valid. To trigger this workflow when the email field value changes, you would select the email field as the event source. In the events configuration, you would choose the "onchange" event, which ensures that the workflow is triggered automatically whenever the value in the email field is updated.

Reference: Workflows