Dynamic fields in workflows

[FHD-MF]

Infos:

• Used Zammad version: Zammad Version 6.3.1-1715754184.27f4405b.bookworm
• Used Zammad installation type: package
• Operating system: Debian 12 (Bookworm)
• Browser + version: Firefox 129.0

Expected behavior:

• Hidden fields will get shown upon selecting a specific entry in a select field

Actual behavior:

• Nothing happens

Steps to reproduce the behavior:

• Create a new text attribute on the ticket object for example “Inventory Number”
  • Select that its hidden by default
• Create a new select attribute on the ticket object (Type of Ticket)
  • Select that its hidden by default
• Create two workflows
  1.
  • Object: Ticket
  • Condition: organization is specific Company xyz
  • Action: Show ticket type
  • Priority: 500
  • Everything else default (stop after match: no, active: active)
  • Object: Ticket
  • Conditions:
    1. organization is specific Company xyz
    2. ticket type is “problem with computer”
  • Action:
    • Show inventory number
    • Set mandatory inventory number
  • Priority: 501
  • Everything else default (stop after match: no, active: active)

There was a similar thread a while ago which didn’t get resolved: Dynamic fields in tickets - #2 by ecomsilio

[FHD-MF]

If I try to create a ticket as a test user without the mandatory attribute I get an error message “Error ID xyz: Please contact your administrator”.

The error in the logs is Error ID xyz: Missing required value for field 'abcd'!

[dominikklein]

Normally the described use case as a common thing and at least in my last tests it was working fine. Maybe we need some detail information about the configuration. Could be an screenshot from the object attribute configuration and the core workflows?

[FHD-MF]

Thank you for the quick response
Creating a ticket:

Select attribute which should show the other options after selecting “Neuer Mitarbeiter”:

Workflow that enables the select field if the organization is xyz:

One of the attributes that should be visible after “Neuer Mitarbeiter” gets selected:

Core Workflow that should activate fields when “Neuer Mitarbeiter” gets selected:

[FHD-MF]

Fixed by upgrading zamamd