cancel
Showing results for 
Search instead for 
Did you mean: 

Why is aspect not applied ?

sobotka
Champ in-the-making
Champ in-the-making
Hi,
I have the following situation:

I definied a new role "Taster" which is like standard "Consumer" but does not allow to read the content itself:

      <permissionGroup name="Taster" allowFullControl="false" expose="true" >
           <includePermissionGroup type="sys:base" permissionGroup="ReadProperties"/>
           <includePermissionGroup type="sys:base" permissionGroup="ReadChildren"/>
      </permissionGroup>

Then I have a custom aspect "A" which adds some attributes (let's see only a fragment of it):

      <aspect name="my:A">
         <title>A</title>
         <parent>cm:titled</parent>
         <properties>
            <property name="kmx:keywords">
               <title>Key words</title>
               <type>d:text</type>
               <mandatory>true</mandatory>
            </property>
         <overrides>
            <property name="cm:title">
               <mandatory>true</mandatory>
            </property>
            <property name="cm:description">
               <mandatory>true</mandatory>
            </property>
         </overrides>
      </aspect>

Now I have a space "S1", where:
- I set a rule to apply the aspect "A" on a content
- I set EVERYONE to be a "Taster" (new role defined above)

Next I have a space "S2" which is a subspace of "S1". There:
- I set EVERYONE to be a "Collaborator"

Now when a user creates a new content within "S2", the aspect "A" is not applied automatically ! (It can be applied manually.)
WHY ??

If I change in "S1" EVERYONE to be a "Consumer", the aspect "A" is applied automatically when a user creates a new content within "S2" !
WHY ??
The difference between Consumer and Taster roles is that Consumer icnludes:
           <includePermissionGroup type="sys:base" permissionGroup="ReadContent"/>
But what has this ReadContent permission to do with aspect application ??

Thanks for any hint.
Petr
5 REPLIES 5

sobotka
Champ in-the-making
Champ in-the-making
Some news:

If I create a space "S0" above "S1" where:
- I set rule with aspect "A" to be applied on a content
- I set EVERYONE to be a Consumer

Than it works ok. (On "S1" EVERYONE is a Taster, on "S2" EVERYONE is a Collaborator.)

It seems that it is important taht the rule is applied on the same space where EVERYONE is at least a Consumer …

Is this all a bug ??

Petr

sobotka
Champ in-the-making
Champ in-the-making
Now I created another rule (to send a notificaton e-mail) and it has the same problem.
The conclusion I wroted above holds true, in other words:

The rules are applied only if on the space where the rule is defined the user has at least the Consumer permissions.

Seems to me to be a bug …
Petr

erictice
Champ in-the-making
Champ in-the-making
It seems correct.  You wouldn't want someone that doesn't have permission to edit a space to create rules on it.  What permissions does the user you are creating this rule with have on the subsequent folders?

sobotka
Champ in-the-making
Champ in-the-making
It seems correct.  You wouldn't want someone that doesn't have permission to edit a space to create rules on it.  What permissions does the user you are creating this rule with have on the subsequent folders?

Hi, thanks for your reaction.
It might be that I didn't explained the think correctly.

I don't want the user (being EVERYONE) to create the rules. I want him to create contents within the space "S2". He is able to create it, but the rules inherited into this space "S2" from space "S1" are not applied automatically when the user creates the content. But he can apply them afterwards manually (using Run Action), so the problem is not in user permissions.

Is it clearer now ?
Petr

sobotka
Champ in-the-making
Champ in-the-making
Hmmm, is there someone from Alfresco developers who could give me an answer for this issue ?
Is it bug ???
Petr
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.