Modifying security dimensions
Depending on how your deployment of i2 Analyze is configured and what your aims are, modifying the security dimensions in the security schema can require different approaches. The implications of any changes, for you and your users, can also be different.
Permitted changes to security dimensions
The following table shows the changes that you can make to the dimensions in the security schema of a deployed i2 Analyze server. Some changes to ordered dimensions require you to re-create the search index, which can be time-consuming.
Making a change that's not allowed requires clearing the data from the system. It's important to be sure about the security dimensions you need before you go into production!
The table is written in terms of how dimensions and dimension values are defined in the security schema XML file. However, the same rules apply when the values from a dimension values provider change.
Change | XML elements or attributes | Allowed | Reindex? |
|---|---|---|---|
Add a security dimension | <Dimension> | No | N/A |
Modify an existing security dimension | DisplayName, Description, ResolutionMode | Yes | No |
Remove an existing security dimension | <Dimension> | No | N/A |
Add a dimension value to an unordered security dimension | <DimensionValue> | Yes | No |
Add a dimension value to an ordered security dimension | <DimensionValue> | Yes | Yes* |
Reorder the dimension values in an ordered security dimension | <DimensionValue> | Yes | Yes |
Modify an existing dimension value | DisplayName, Description | Yes | No |
Remove an existing dimension value from a security dimension | <DimensionValue> | Yes | No** |
Restore a previous dimension value to a security dimension*** | <DimensionValue> | Yes | No |
Move an existing dimension value between security dimensions | <DimensionValue> | No | N/A |
* If you add a dimension value to the bottom of the sequence in an ordered security dimension, you do not need to complete a reindex.
** Removing a dimension value does not require a reindex, but you should update any ingested data so that it does not use that value. See What to do next after editing the security schema file.
*** If you restore a dimension value to an ordered security dimension, you must also restore the previous order to avoid a reindex.