Customizing the User Console › Configuring Profile Tabs and Screens › Additional Components in a Profile Screen › Add a History Editor Field

Add a History Editor Field

The history editor is a text area which creates new history entries, if this text area contains text when the task is submitted. The history editor can include an optional submit button, which allows the creation of history entries without submitting the task.

To add a history editor field to a profile screen

1. Modify a profile screen.
2. Select a field to modify or add a new field.
3. Select (Separator) in the Attribute Name field.

   CA Identity Manager changes the fields that are displayed.

4. Select History Editor in the Style field.
5. In the Label field, enter the name of the history editor field that appears in the profile screen.
6. Enter text that is attached to history log entries which describes the role of the user who created the log entry in the Stakeholder field.

   For example, the following description would appear in the Source column of a history display for a user with an Approver stakeholder label:

   User comment by SalesMgr (John Doe) acting as Approver

   This can be a string or a localization key, specified according to CA Identity Manager localization rules. The stakeholder type is blank by default, and is optional.

7. Enter the number of rows and columns for the history editor.

   Note: If you do not specify a value for rows and columns, the history editor does not display properly in the profile screen.

8. Select one of the following options in the History Level field:
   • Task Level—For approval tasks it is the task belonging to the event being approved. For non-approval tasks, this is the current task.
   • Event Level—For approval tasks, this is the event being approved. For non-approval tasks, this returns no results.
9. Specify the text that appears on the submission button in the Add Button Label field.

   The text can be a string or a localization key, specified according to CA Identity Manager localization rules. If it is blank (the default value), then the button label is "Add History Event".

10. Specify the CSS class to use to for the Add button in the Add Button CSS Class field.

    These strings will be included in the <input> element in the profile screen, as the contents of the class and style elements respectively.

11. Specify the CSS class to use to for the Add button in the Add Button CSS Style field.

    These strings will be included in the <input> element in the profile screen, as the contents of the ‘style’ and ‘class’ elements respectively.

12. Specify whether the history editor includes its own independent Add button by checking or unchecking the Enable Add Button field.

    If checked, this button submits only the new history entry, not the entire task.

More Information:

Add a History Display Field