Conditionally hide fields in all views via core workflows

[Dreamtrail]

1. What is your original issue/pain point you want to solve?
   I hide fields with the core workflows in the create and edit screen using other fields. e.g.: multiselect contract 1 and 2 For contract 2, the text fields 1 and 2 should be displayed but not if only contract 1 is active.
   However, this does not work if I am in the ticket dialog or on the organization page itself. Here the fields are either always or never displayed in connection with the field permissions.

2. Which are one or two concrete situations where this problem hurts the most?

• if we have not concluded contract 2 with the customer, we do not need to see text fields 1 and 2 (too many unnecessary fields visible).
• At first glance, you might overlook the fact that contract 2 is not active because text fields 1 and 2 are still displayed

3. Why is it not solvable with the Zammad standard?
   Core workflows only apply at creation and edit masks

4. What is your expectation/what do you want to achieve?
   Hide unnecessary fields where I don’t need to see them

[Robz]

Works perfectly fine for me to show/hide fields from Ticket/Org/User view, example:

Works perfectly fine for me to add/remove fields based on conditions as well, example:

Are you using the show/hide and conditions/actions correctly?
Please show your workflow so we can see.

[Dreamtrail]

Workflow:

EditPage Value selected

EditPage Value not selected

ViewPage Value selected

ViewPage Value not selected

[Robz]

You are correct! My bad.

To change View settings you need to go to Settings > Objects > Organizations

However, it’s limited what you can edit here. Another workaround, not recommended, is to create a custom .CSS to hide the field you don’t want.

field.name { display: none }

If this is a conditional field to hide for certain organizations only, then you have a pickle to see if you can make something smart, maybe something like if field is empty then hide (if conditions like that is possible through CSS, not my strongsuit)

(Remember to enforce new .css files in nginx/apache or clear network data if changed CSS is not visible, and backup your custom CSS as it might be overwritten/removed when upgrading Zammad)