Hey, 3 years later lol.
Is the feature of having specific display rules in the Options of collection, got removed or changed? As i have lots of collections with many options but only one or two options differs based on operationā¦ and seems redundant to duplicate that collection multiple times with small differences .
As now if i did it, i get:
Problem running workflow
Could not resolve parameter dependencies. Max iterations reached! Hint: If
displayOptions
are specified in any child parameter of a parentcollection
orfixedCollection
, remove thedisplayOptions
from the child parameter.
This is a snippets of one of the implementation needs for it:
{
displayName: 'Transaction Call Settings',
name: 'transactionSettings',
type: 'collection',
placeholder: 'Add Transaction Settings',
default: {},
displayOptions: {
show: {
resource: ['transactions'],
operation: ['createTransaction', 'updateTransaction'],
},
},
options: [
{
displayName: 'Error If Duplicate Hash',
name: 'error_if_duplicate_hash',
type: 'boolean',
default: true,
description: 'Whether to throw an error if a duplicate hash is detected',
displayOptions: {
show: {
resource: ['/transactions'],
operation: ['/createTransaction'],
}
},
},
{
displayName: 'Apply Rules',
name: 'apply_rules',
type: 'boolean',
default: false,
description: 'Whether to apply rules to the transaction',
},
{
displayName: 'Fire Webhooks',
name: 'fire_webhooks',
type: 'boolean',
default: true,
description: 'Whether to trigger webhooks for the transaction',
},
{
displayName: 'Group Title',
name: 'group_title',
type: 'string',
default: '',
description: 'Title for grouping split transactions',
},
],
},