Override Visibility Strategy while initializing Sugar Bean

Question

Hello Folks,

I wanted to override visibility strategy defined in module bean class definition while initializing that bean.

For eg: I have a module called Test and I have defined following visibility in bean class.

class Test extends SugarBean

{

public function __construct()

{

$this->addVisibilityStrategy("OwnerVisibility");

parent::__construct();

}

Now, while initializing bean, I wanted to override this strategy in some scenarios.

$testBean = BeanFactory::newBean("Test");

$testBean->addVisibilityStrategy("OwnerOrAdminVisibility");

But the above line is not working. I am not sure how to override the visibility already defined in bean definition.

Any help or idea would be greatly appreciated.

Regards.

Hats

Hatim Alam · Accepted Answer

hats , After additional review it looks like ./data/visibility/OwnerOrAdminVisibility.php (that extends OwnerVisibility) are internal only visibility classes that you should not use. They are applied to modules that do not have real data requirements and do not implement search engine filtering for that reason. As I was saying before, you need to make sure you implement correctly the visibility also on the search engine Elasticsearch. I encourage you to look at the previously posted example where it implements the required "elastic*" methods. If I had different needs that change based on some user's parameters I would write my own visibility class and apply my conditional logic in there to behave differently based on the required conditions and that implement correctly the visibility on the search engine as well. As mentioned previously I highly recommend you to complete profiling at scale as any visibility change (if not completed correctly) might make the system under perform. Hope it helps