Hi,

You can simplify your process as follows.

1- Add a boolean field in the 'account.move'. It should be a computed field and made invisible in the form view. Add the compute function and add all your conditions in the function.

This field will encapsulate your condition logic (e.g., move_type == 'out_invoice'). It will be used to control field visibility in the view.

     class AccountMove(models.Model):

    """Inherited model 'account.move'."""
    _inherit = 'account.move'

    is_check_condition = fields.Boolean(string="Check Condition",
                                      help="Compute field for check the field conditions",
                                      compute="_compute_conditions")
    # Add your custom fields
    
    
    def _compute_conditions(self):
        """Compute field for checking the field visibility of the custom fields"""
        for rec in self:
            if rec.move_type == 'out_invoice': #Add all the condition that make the boolean field True
                rec.is_check_condition = True
            else:
                rec.is_check_condition = False

2- Add the computed boolean field as the invisible attribute of the custom fields.

<record id="view_move_form" model="ir.ui.view">
    <field name="name">account.move.form.inherit</field>
    <field name="model">account.move</field>
    <field name="inherit_id" ref="account.view_move_form"/>
    <field name="arch" type="xml">
        #Add the compute field and make it invisible
        <xpath expr="//group[@id='header_right_group']" position="inside">
            <field name="is_check_condition" invisible="1"/>
        </xpath>
        # Add the boolean field as the condition for the custom field
        <xpath expr="//#" position="inside">
            <field name="custom_field" invisible="is_check_condition"/>
        </xpath>
    </field>
</record>

If you have multiple distinct conditions, you can create multiple computed booleans.This way, different sets of fields can reference different visibility flags.

Hope it helps.

Hi.
Managing large views is always hard especially when the conditions start to increase exponentially. 

Someway you can make the process easier:

Option 1: Define a new selection field that tracks each workflow, and have a computed action for changing the visibility of the other fields, or set any rules you might have (domains, fields values, etc
).
This lets you define each process with a single user action, and every aspect of that workflow is embedded into a single function.

Option 2: Create one view per workflow type.
As before, this gives you more control over each workflow. The negative part is that you increase maintenance difficulty, as your fields are replicated through more locations, but for some cases this works well.