Previous Topic: Begin Service Creation

Next Topic: Define Admin Policies for the Service

Define the Service Profile

On the Profile tab, you define basic characteristics of the service.

Follow these steps:

  1. Enter a name and tag. A tag is a unique identifier for the service.

    Note: Tags can only contain alphanumeric and underscore characters, and cannot start with a number. Once created, a tagname cannot be changed, or reused, even if a service is later deleted.

  2. Select Enabled if you want to make the service available to users as soon as you create it.
  3. Select Self Subscribing if you want this service to appear in the list of services available for users to request. When Self-Subscribing is enabled, users can request access to this service through the User Console.
  4. If desired, add one or more categories. Type a category name and click the up arrow to add it to the service.

    Categories add additional information to a service. You can use this additional information to facilitate service searches in environments that include a significant number of services.

  5. Complete any other custom attributes that are defined for the service.
  6. Specify a duration if you want this service to expire within a specified period after a user first receives it. Click Add, then specify a time interval for the service.

    Note: The service expiration is calculated from the date the user first receives the service, not from the date the user requests the service.

  7. (Optional) To have an email sent to users before their service expires, add a notification period.

    Specify multiple notification periods to send multiple emails.

    For example, you can send an email one week before a service expires, then send another email the day before the service expires.

    Note: To send notifications before a service expires, configure the Email tab in the Create or Modify Service task.

  8. Specify a Service Run-time User Data Screen if you want to collect additional user data at the time a user requests the service.

    Use a Service Run-time User Data Screen to help ensure that all user data necessary to fulfill the service exists in the system. For example, a valid email address is required to fulfill a service that creates an account in Google Apps. If an email address for a user does not exist in the CA IdentityMinder user store, the user is required to provide it when requesting the service.

    1. Click Browse.

      A list of available profile screens appears. These screens are typically used to collect user data.

    2. Select a profile screen that contains the user data you want to collect. Choose one of the following options:
      • Click Select to collect all user data contained in that screen.


      • Click Copy to customize the user data you want to collect. Specify a name and unique tag for the new screen. Add, edit or remove user data elements, and click OK.


      • Click Edit to change the user data contained in that screen. Add, edit, or remove user data elements, and click OK.

      Important! If you edit a user data screen, your changes apply everywhere the screen is used in the User Console. Consider copying and customizing the profile screen instead.

    3. Click Select.

      The user data elements that you selected are collected at the time the user requests the service.

      Note: If the required data exists in the system when a user requests the service, the data is prepopulated in the profile screen.

  9. Define Admin Policies for the Service.