Adding `dataaudit` post-installation?

Hi,

I was wondering if the `dataaudit` setting can be added to an Entity (or Entity Property), using the `@Config` (or `@ConfigField`) Annotation, after the `oro:install` has been run.

In other words, does app/console oro:entity-config:update --force pick up on those changes?

Thanks,
Nick

Topic

[Yurii MuratovParticipant]

Hi, @nick_mallare.
During of oro:entity-config:update –force execution, will be collect only Config annotations from the new entities.
If you want to update entity config, you should write migration for updating some parameter of your entity.
An example of such migration:

https://github.com/laboro/platform/blob/master/src/Oro/Bundle/EmailBundle/Migrations/Schema/v1_11/UpdateEmailSecurity.php

In this example we set value ‘VIEW;CREATE;EDIT’ for parameter ‘permissions’ from the scope ‘security’ for ‘Oro\Bundle\EmailBundle\Entity\Email’ entity.

[Nick MallareParticipant]

Hi Yuril,

I don’t have access to laboro. Can you post a Gist, please?

Thanks,
Nick

[Nick MallareParticipant]

Is this what you were referring to?

https://gist.github.com/nmallare/266a36d7cc4dc4bd870b

Thanks,
Nick

[Yurii MuratovParticipant]

Sorry, it’s my mistake.
Correct link – https://github.com/orocrm/platform/blob/master/src/Oro/Bundle/EmailBundle/Migrations/Schema/v1_11/UpdateEmailSecurity.php

Yes. You are correct with your gist.

[Nick MallareParticipant]

And, just to make sure. The `dataaudit` property, at the Entity level, can be changed via this method?

Thanks,
Nick

[Yurii MuratovParticipant]

Yes. dataaudit – is the scope, and in this scope we have a parameter auditable

[Author]

Replies