Add non mandatory aspect to content type

[d_franz]

Hi

I whant to add a aspect to a content type, so it is applyed to it directly after creation. But I don't whant this aspect to be mandatory, so I can remove it in a later state.

Is there a possibility to add a aspect beside "<mandatory-aspects>"?

Thanks!

[mitpatoliya]

Yes, surly you can do that.
If you do not mention the aspect in the content model as mandatory aspect it will not be a mandatory.
And as you can always add and remove aspects on the fly on any content type.
You might have seen the actions add and remove aspects that will give you required hint.

[d_franz]

I know that I can apply an aspect to any content type. My problem is that I have to run a script for this. And for default I can only trigger such a script (java-script with a folder rule) after saving changes in the meta-data.
But I want that the content has this aspect directly after applying a custom content type to it. On a later state I want to remove some of these aspects with a script.

[mitpatoliya]

You can have rule which will trigger when new content with particular content type (your custom content type) is created or entered in that folder
add your custom aspect to it.
Then you can remove it whenever required.

I think your problem is you do not want to create rule on any particular folder and want to make it generic for whole repository is that correct?

[luyanda]

I have a rule set to attach the aspect to the content that is created into the folder, now its not working properly. i have done my configurations and when i create content i have to manually mange the aspect.
Please look to the attached files

Please help me to rectify this problem.