Partition Settings
Non-partitioned information can be accessed and updated by all Analysts.
It is important that you consider seriously how you want to partition your database, as partitioned information is restricted to Analysts with access to that partition.
You will need to contact Alemba® Support if you want to disable partitioning at any point.
The options that you can select for partitioning are grouped by:
IPK (If IPK status/streams are not enabled, these options relate to calls)
CMDB
Request
Tasks
SLM
General
Self Service Portal
IPK Workflow Rules cannot be partitioned, and will be available across all partitions. The Analyst who sets up the rules will therefore have access to create rules from data fields from all partitions, including those to which they do not have access. *This does not mean they can see sensitive data, but they can build rules against the data fields.
Partitioning IPK
Choose the settings you wish to use. These are options that enable you to partition your database based on call or IPK information, if IPK status/streams are enabled:
Call Details | Calls are assigned to the partition of the Analyst who logs them. A call retains its original partition even when it is forwarded to or actioned by an Analyst in a different partition. Selecting this options enables the Change Call Partition option within the IPK Management security role. This checkbox is unavailable if you have selected to partition by screen set |
Call Screen Set | Analysts will only be able to access the call screen sets configured for the partitions to which they have access. This checkbox is unavailable if you have selected to partition by screen set |
Call Templates | Analysts will only be able to access the call templates linked to their partition. This checkbox is unavailable if you have selected to partition by screen set |
Custom Call Profiles | Partitions the Custom Call Profile fields that can be added to Call Details windows configured in ASM Designer |
Urgency, Impact, and Priority | If you are using the ITIL IPK Tiers module, you will probably have priority automatically derived from the Urgency and Impact fields on a call. All these three fields can be partitioned in ASM Core. If you are partitioning by Priority, Analysts can see priorities from all partitions when they assign specific colors to priorities. This is because an Analyst may be forwarded a call with a priority in another partition. This applies to priority for calls, requests, and tasks. |
IPK Partition Settings | Enables you to set different IPK Settings for each partition on your system. You can configure these settings for a particular partition through IPK Settings (Partitioned). The settings are then available to Analysts with access to the partition. This checkbox is unavailable if you have selected to partition by screen set The IPK Settings for a particular partition can only be updated by a System Administrator working within that partition. If this option is not selected, only the analyst logged in as ADMIN can configure settings for the “Unspecified” system partition. |
Type, Question Map, Call Status Titles, Reasons | When a call is logged in a particular partition, the available values in the corresponding fields are those that are defined for the partition in which the call is logged |
IPK Streams | Enables definition of different streams in different partitions. Only streams defined for that partition are available. |
Change Partition on Take Action | Call Details must be selected to enable this option. This checkbox is unavailable if you have selected to partition by screen set The partition of a call is automatically set to the partition the Analyst is working in when they take action on a call. All Analysts in the Group to which partitioned calls are forwarded will be able to view the calls but only Analysts with access to the current partition of the call may take action on it. When a call is actioned by an Analyst in a different partition to the call, any values that have been specified for the previous partition will still display. However, Analysts can only update the call using values available in their current working partition. |
Partitioning CMDB Item
Select any of the items listed to ensure that they are added to the partition of the Analyst who creates them and will only be available to other Analysts who have access to this partition.
If you selected to partition by screen set, when you create, say, a User from the Call Details window, the User is added to the partition of the call, not necessarily your partition.
CMDB Items created from resources discovered on an External Source are assigned the source’s partition. If the source is not partitioned, the CMDB Items inherit the partition through the template assigned to them, if a partition is assigned to the template. If a source is partitioned but CMDB Items are not, CMDB Items created from the external source are not partitioned.
If you are using the Asset Management Module, asset Transactions made against asset CMDB items are created in the partition of the CMDB Item.
Partitioning Request
Select any of the items listed to ensure that they are added to the partition of the Analyst who creates them and will only be available to other Analysts who have access to this partition.
Request | Requests are added to the partition of the Analyst who logs them. A request retains its original partition even if it is forwarded to or actioned by an Analyst in a different partition. Selecting this option will automatically select the Task option in the Task group. Once selected, it cannot be deselected. If you select it by accident, close the window without saving. This checkbox is unavailable if you have selected to partition by screen set |
Request Screen Set | Analysts will only have access to request screen sets that are configured for the partition they log in to. This checkbox is unavailable if you have selected to partition by screen set |
Workflow Templates | Analysts will only have access to the workflow templates in the partition in which the request is logged. This checkbox is unavailable if you have selected to partition by screen set |
Request Type, Request Risk, Request Priority, Request Activity, Request Implementation Profile, Request Status, Request Extension Profiles 1 to 4 | When a request is logged in a particular partition, the values available in the corresponding fields for selection are those that are defined for the partition in which the request is logged, and to which the Analyst has access. |
Change Calendar | You can define different change calendars in different partitions. Analysts will only have access to those change calendars that have been created in the partitions to which they have access. |
Change Partition on Take Action | The partition is automatically set to the partition the Analyst is working in when they take action on the request. All Analysts in the Group to which partitioned requests are forwarded will be able to view the request but only Analysts with access to the request’s original partition may take action on it. This checkbox is unavailable if you have selected to partition by screen set When a request is actioned by an Analyst in a different partition to the request, any values that have been specified for the previous partition will still display. However, Analysts can only update the request using values available in their current working partition. |
Partitioning Task
Select any of the items listed to ensure that they are added to the partition of the Analyst who creates them and will only be available to other Analysts who have access to this partition.
Task | This is automatically selected when the Request checkbox is selected, and disabled if the Request checkbox is cleared. A task retains its original partition even if it is forwarded to an Analyst in a different partition or actioned by an Analyst in a different partition. If the Change partition on Take Action box is ticked for the Request, all of the tasks will move also. |
Task/Approval Type, Task Priority, Task Phase, Task Activity, Task Defer Status, Task Extension Profiles 1, 2, 3, and 4 | When a task is logged in a partition, the values available in the corresponding fields for selection are those defined for the partition in which the task is logged, and to which the Analyst has access. |
Partitioning Agreement/SLM
Agreements and agreement matrices cannot be partitioned if you are partitioning by screen set.
Select any of the items listed to ensure that they are added to the partition of the Analyst who creates them and will only be available to other Analysts who have access to this partition.
Agreements | Links agreements to the partition of the Analyst who creates them. This checkbox is unavailable if you have selected to partition by screen set |
Agreement Matrix | Partitions the matrices that drive the escalation and breach times from an agreement. Analysts will only be able to apply a matrix to an agreement if the agreement and matrix are in the same partition. If any element in an agreement matrix (such as a configuration item) is partitioned, the matrix will be partitioned automatically, even if you have not selected this checkbox. This checkbox is unavailable if you have selected to partition by screen set |
Working Hours and Public Holidays | When an Analyst creates an agreement, only the working hours and public holiday schedules in the same partition as the agreement are available for selection. |
Exclusion Reasons | Limits Analysts to exclusion reasons in the same partition as the agreement. Exclusion reasons are defined in Service Level Management administration. |
Partitioning General Options
Select any of the items listed to ensure that they are added to the partition of the Analyst who creates them and will only be available to other Analysts who have access to this partition.
| Knowledge Bank | Restricts Analysts to Knowledge Bank search results in their partition. Knowledge entries will be added to the current partition of the Analyst creating the entry. |
|---|---|
Security Profiles | Restricts Analysts to selecting only those profiles that are defined in the partition in which the call, request, or task is being logged. |
Security Roles | Roles are created in the partition you have chosen to work in as System Administrator. The role will be available in the partition in which it is created. However, it may be linked to groups and people from different partitions. Analysts can only be assigned a security role that is in one of the partitions to which they have access. |
Bulletin Board | Analysts will only be able to read (and edit, if they have sufficient permissions) messages posted in the partitions to which they belong. |
Attributes | Partitions attributes for all the entities that can be partitioned and have for which attributes can be defined. |
Email Templates | Partitions the message templates that are used when sending an outgoing email for all the entities that can be partitioned, and from which an outgoing email can be sent. |
Outgoing Email ID | Partitions the Sender Email IDs that are used when sending an outgoing email for all the entities that can be partitioned, and from which an outgoing email can be sent. |
Forward to Group Members Included | Enables Analysts to view calls, requests, or tasks that are forwarded to any group of which they are a member, including those forwarded to a partition to which the Analyst does not have access. Alemba® recommends that organizations which implement a Shared Services model select this option. |
Partitioning Self Service Portal
Options in this section also apply to Users who are accessing the portal. For more information, contact Alemba® Support.
Specify in which partition(s) information on the Self Service Portal can be submitted or viewed.
Use Analyst’s Partition |
|
Display results from All Partitions |
|
Filter Results by Template Partition |
|