Adding a new view using existing policies

To add a new view that is accessible by roles with existing role-based View policies, create an XML file.


<?xml version="1.0" encoding="ISO-8859-1" standalone="no" ?> 
<!DOCTYPE Policies SYSTEM "../dtd/accesscontrolpolicies.dtd">

<Policies>

        <Action Name="MyNewView" CommandName="MyNewView">
        </Action>
   
        <ActionGroup Name="ProductManagersViews"
OwnerID="RootOrganization">
              <ActionGroupAction Name="MyNewView"/>
        </ActionGroup>

</Policies>

Procedure

Create a new action definition in the XML file that has the view name MyNewView. This can be any name that you choose.
```
<Action Name="
MyNewView"
        CommandName="
MyNewView">
</Action>
```
Determine which roles should have access to this view, and associate the new action with the corresponding action groups in the XML file as in the following example:
```
<ActionGroup Name="ProductManagersViews"
OwnerID="RootOrganization">
        <ActionGroupAction Name="
MyNewView"/>
</ActionGroup> 
```
There is already a role-based policy, ProductManagersExecuteProductManagersViews, that includes this action group, so a new policy does not have to be created. Also, the default role-based policies belong to the ManagementAndAdministrationPolicyGroup policy group which applies to most, if not all, of the organizations in the site, so no further policy group subscription is necessary.
Load your XML changes into the database. For more information about loading the XML changes, see Loading access control policy data.
Update the Access Control Policies Registry in the Administration Console by doing the following:
1. Logon to the Administration Console as a Site Administrator.
2. Click Configuration > Registry.
3. From the list of registries, select Access Control Policies.
4. Click Update.