Create or edit an alert type

To create or modify an alert type is a four-step process.

  1. Create views that reflect the columns and rows desired for the new alert type. Follow the steps in Create a new view in the Add tab menu.
  2. Create the alert type and import the views.
  3. Activate the alert type.
  4. Edit the alert type and make it a tracked alert.

Note:

You must have the Manage Signal Configurations permission or be a superuser to access this page. A newly installed Signal Configuration needs to be refreshed once before trying to create views and add alert types.
Create the alert type and import the views
  1. In the left navigation pane, click the Settings icon (Settings icon).
  2. From the Configure System menu, select Manage Signal Configurations.
  3. Click the configuration's Row Action menu (Row Action menu icon), then select Edit Alert Types.
  4. In the top left corner, click Add Alert Type or edit an existing alert type by selecting Edit from the alert type's Row Action menu (Row Action menu icon).
  5. In the Label field, type a unique and descriptive label for the alert type. This will be used as the tab label on the Signal Review Page.
  6. In the Description field, describe how the alert gets populated. This will become the hover help text for the tab.
  7. Oracle recommends that you not select the Tracked alert check box at this point.
  8. For the Alert rules based on field, select the appropriate radio button: Review period or Complexity level / periodicity.
  9. If an alert rule is based on review periods, then note the review period of the first row. If the rule is based on Complexity level / periodicity, note the Complexity level and enter a periodicity value. Open the action menu for this first row and select Import from View.

    Note:

    Review Period rules use the product's review period to determine the alert type rule that is used. The rules are evaluated with each refresh. Complexity level /periodicity rules use the product’s Complexity level to determine the alert type rule used. The product’s birthdate and the alert type rule’s periodicity determine if the alert rule should be considered during refresh. For example, if the product birthdate is February and the periodicity is three months, the alert will be triggered in May, August, November, and February. To be considered for complexity-based alert calculations, a product needs both complexity and birthdate values.
  10. Select the view to be associated with this alert type rule. Oracle Empirica Signal imports the view and populates the Condition, Selected columns, and Sorted by columns.
  11. Repeat steps 9-10 for each Review period or Complexity level / periodicity in the table.
  12. Click Save.

    The alert type appears as the last row of the Edit Alert Types page. The newly added alert type is deactivated by default. This means that Active in next refresh is set to No for the alert type.

Activate the alert type
  1. On the Edit Alert Types page, select Activate for the newly created alert type.
  2. (Optional) If the new alert type replaces an existing alert type, deactivate the previous alert type.

    With the next refresh, the new alert tab will be added.

(Optional) Edit the alert type and make it a tracked alert
  1. In the left navigation pane, click the Settings icon (Settings icon).
  2. From the Configure System menu, select Manage Signal Configurations.
  3. Click the configuration's Row Action menu (Row Action menu icon), then select Edit Alert Types.
  4. To make this a tracked alert, select the Tracked alert check box, provide a one-letter abbreviation, and select a color to associate with the alert type. The abbreviation and color appear on the alert tab and cells on the Product-Event Combinations table as the tracked alert's icon.

    Changes will take effect in the next refresh.