Which code snippet calls the interface APP_RecordDashboard with appropriate values for recordId and firstName using best practices?

Which code snippet calls the interface APP_RecordDashboard with appropriate values for recordId and firstName using best practices?

• A. rule!APP_RecordDashboard( recordId: 2, firstName: "Kyle" )
• B. rule!APP_RecordDashboard( recordId: 1, firstName: "Kyle" )
• C. rule!APP_RecordDashboard( recordId: 1, firstName: Kyle )
• D. APP_RecordDashboard( recordId: 1, firstName: "Kyle" )

Answer: (B)

When you call an interface from a rule in Appian, you should wrap the call with rule! and pass inputs using explicit named parameters with the correct types. The interface APP_RecordDashboard expects a recordId (a number) and a firstName (a string). The best snippet uses the rule wrapper and clearly labeled inputs: rule!APP_RecordDashboard(recordId: 1, firstName: "Kyle"). It ensures the interface runs in the proper rule context, the recordId is a numeric literal, and the firstName is a string literal, which matches the expected types. The other options are less suitable because they either omit the rule wrapper, use incorrect literal types (such as a string not in quotes), or provide a value that may not align with the intended test context (e.g., a different recordId).

When you call an interface from a rule in Appian, you should wrap the call with rule! and pass inputs using explicit named parameters with the correct types. The interface APP_RecordDashboard expects a recordId (a number) and a firstName (a string).

The best snippet uses the rule wrapper and clearly labeled inputs: rule!APP_RecordDashboard(recordId: 1, firstName: "Kyle"). It ensures the interface runs in the proper rule context, the recordId is a numeric literal, and the firstName is a string literal, which matches the expected types.

The other options are less suitable because they either omit the rule wrapper, use incorrect literal types (such as a string not in quotes), or provide a value that may not align with the intended test context (e.g., a different recordId).