Custom objects and workflows not working as expected. Bug?

Infos:

  • Used Zammad version: 5.2.x
  • Used Zammad installation type: Docker Compose
  • Operating system: Windows 10 (latest release)
  • Browser + version: Chrome Version 106.0.5249.62 (Official Build) (64-bit)

Expected behavior:

  • I created objects (“Sender Email”, and “Email Contents”) and unchecked all “Shown” and “Required” checkboxes. I have a workflow set to show the fields when another custom field (Ticket Type>Phishing Report) is selected. “Sender Email” and “Email Contents” fields should not show up unless Phishing Report is selected. (Please see attached screenshots)

Actual behavior:

  • The custom fields (“Sender Email” and “Email Contents”) are showing up most of the time. They will disappear when I select the correct field then click another field (see attached gif). They should only show up in the “Security” group but they are showing up in the “IT” group as well.

Steps to reproduce the behavior:

  • I have tried variations on having it show vs not show but it always has the random behavior. I am hoping this is user error and I don’t know what I am doing (I am new to Workflows and Objects) but it feels like it might be a bug.

One thing of note that might be important. I think I have created and deleted the objects several times as I have tried to get this to work. I think I have kept the names the same. Maybe there is something residual in the database that is causing the odd behavior.

Thanks!



2022-09-29_13-57-10

I would assume this happens because you don’t have a workflow to hide the fields, only one to show them. Effectively you only defined “If the condition happens make the fields visible”. So now the fields are visible but this does not automatically mean that the fields are hidden again when something else happens. You probably need another workflow that is the exact opposite “when the condition is NOT met HIDE the fields and make them NOT mandatory” so everything is reversed that was set before. You could try to achieve this in a single workflow by using NOT and the HIDE action but I don’t know if it will work the way you need it. You have to play around with it and you will have to set the fields to “shown” in the object properties.

Thanks so much for your reply @awedor! I played around with your ideas and got things working much better. There are still a few places where it is buggy and shows objects when it should not but you have pointed me in a better direction than I was going. I will keep playing around with this.

Thanks again!

1 Like