---
title: "OAPPropEditClass"
slug: "api/basket/types/oappropeditclass"
sidebar:
  order: 373
---

<a id="ref-94a92df4cee0"></a>
<a id="ref-f6a042899aa6"></a>
<a id="ref-067e9569cd2a"></a>

## Synopsis

```text
OAPPropEditClass (
    string propClass,
    boolean visibleOnly,
    boolean editableOnly
)
```


Field propClass of [OAPPropEditProp](/pCon/configuratorOnline/specs/api/basket/types/oappropeditprop) is optional. If missing (currently always the case) or empty, clients should either ignore the property class (e.g. if comparing property class and name with instances of [Property](/pCon/configuratorOnline/specs/api/basket/types/property) as returned by operation [getArticleData](/pCon/configuratorOnline/specs/api/basket/operations/getarticledata)) or specify an empty property class in situations where a property class must be specified (as required by operation [setPropertyValue](/pCon/configuratorOnline/specs/api/basket/operations/setpropertyvalue)).

Fields visibleOnly and editableOnly are used to restrict the visibility of individual properties in OAP property editors. If visible and editable are the property-specific flags reported as fields of complex type [Property](/pCon/configuratorOnline/specs/api/basket/types/property), then the corresponding property must be visible if and only if the expression

(visible \|\| !visibleOnly) && (editable \|\| !editableOnly) is true. Or, perhaps more intuitive, they must be hidden if

(visibleOnly && !visible) \|\| (editableOnly && !editable) is false.
