Dynamic Fields Configuration in Fuuz Screen Designer

Introduction

Dynamic Fields in the Fuuz Screen Designer are essential for optimizing performance and ensuring a smooth user experience. This guide will help you understand how to configure Dynamic Fields effectively.

Key Concepts

1. Payload Array

   • Definition: Fields coming in as the payload to the transform.
   • Usage: Any field directly referenced in the transform.
   • Common Examples:
     • Table's rowData
     • Form's Filter Transform id
   • Note: The transform payload can also be referenced by $ or $ (e.g., $.id or $.rowData).

2. Context Array

   • Definition: Fields coming from the transform context.
   • Usage: Any field from a "variable" starting with $.
   • Common Examples:
     • $components
     • $metadata
     • $parent
   • Important: When referencing context fields in a transform's Dynamic Fields, use the full path without the $ at the start. For example, if your transform uses $components.Form1.data.id, your Dynamic Fields should look like this: json { "payload": [], "context": ["components.Form1.data.id"] }

Best Practices

• Avoid Using $ at the Start: Do not put $ at the start of components in the Dynamic Fields of a transform.
• Optimize Arrays:
  • If your transform isn't referencing anything from the payload, set the payload array to [].
  • Similarly, if not referencing anything from the context, set the context array to [].

Purpose of Dynamic Fields Arrays

The main purpose of the Dynamic Fields arrays is to enhance performance by preventing unnecessary reruns of your transform. Your transform will only run when a field referenced in either array changes, pulling the same value from the cache if nothing has changed.

By following these guidelines, you can ensure that your transforms are efficient and your user experience remains smooth.