Which client-side assets apply to record producers in the catalog context?

Which client-side assets apply to record producers in the catalog context?

• A. Catalog Client Scripts, Catalog UI Policies
• B. Catalog Client Scripts
• C. Catalog UI Policies
• D. Catalog Actions

Answer: (A)

Record producers in the catalog context use the same client-side customization mechanisms as other catalog items. Catalog Client Scripts run in the browser when the producer form loads or fields change, letting you set defaults, perform validation, or react to user input without a server round trip. Catalog UI Policies provide declarative rules to show/hide fields or mark them required or read-only based on other field values, directly on the producer form. Because these are the tools designed to shape the user interface and behavior of catalog forms, they apply to record producers just as they do to standard catalog items. Catalog Actions aren’t primarily client-side UI rules for the producer form, so they aren’t considered the client-side assets here.

Record producers in the catalog context use the same client-side customization mechanisms as other catalog items. Catalog Client Scripts run in the browser when the producer form loads or fields change, letting you set defaults, perform validation, or react to user input without a server round trip. Catalog UI Policies provide declarative rules to show/hide fields or mark them required or read-only based on other field values, directly on the producer form. Because these are the tools designed to shape the user interface and behavior of catalog forms, they apply to record producers just as they do to standard catalog items. Catalog Actions aren’t primarily client-side UI rules for the producer form, so they aren’t considered the client-side assets here.