RSE User Action Management

With iSphere RSE User Action Management you can export some or all user actions from your workspace to a repository. A repository is an XML file on your local PC or a network drive. You can then import some or all user actions from a repository to your workspace. The repository can act as a backup for your user actions.

Here are some other scenarios where you might find User Action Management useful:

Your workspace is corrupted and you need to create a new one. In this case you can export your user actions from the old workspace and import them into the new one.
You want to share your user actions with your colleagues.
You have RDi installed on a computer in your office and at home and want to synchronize your user actions.

To open the iSphere RSE User Action Management dialog, open the iSphere menu click on the Sun icon labeled with RSE User Action Management.

Choosing what to Manage

You now need to specify what you want to manage, and also the repository name:

Editing Area

The user actions in the workspace and in the repository will be displayed in up to four separate horizontal panes.

Edit workspace and repository user actions
Edit only workspace user actions
Edit only repository user actions

Click the appropriate button. The default, Edit workspace and repository user actions, is suitable for the first time you want to create a new repository. With this option you can:

Push user actions from the workspace to the repository and vice versa.
Delete user actions from the workspace.
Delete user actions from the repository.

The next two option, Edit only workspace user actions and Edit only repository user actions are suitable for removing commands from the workspace or the repository.

Profile

Select the profile that contains the user actions you want to manage.

Single Domain

If this is checked, then you will need to select a domain using the Domain drop down. Only user actions of the selected domain will be considered for action.

If this is unchecked, then all user actions will be considered for action.

Domain

Use this option to specify the domain you want to manage, when Single domain is checked.

Repository

Specify the location and name of the repository. A single domain repository must have a suffix of .rseuda and a repository for all user actions must have a suffix of .rseudaall.

Managing User Actions

Basically managing user actions follows the pattern of managing filters. Therefore you are asked to refer to chapter RSE Filter Managing to see how managing RSE resources works.

The editing area for resources that are in the repository and the workspace but with different parameters is a little different from the one used in the filter manager, because user actions have a lot of attributes that can be different. In order to see all differences between a repository and a workspace user action, you can open a compare dialog by double-clicking the user action entry.

Alternatively you can open the compare dialog from the context menu of the user action entry.

Rules For Editing User Action

Editing user actions enforces a few more rules compared to editing filters because of IBM supplied user actions, which intentionally cannot be deleted from the workspace. The user action editor uses the following icons for decorating actions:

- IBM supplied user action

- User defined user action

Attributes Compared Between Workspace And Repository User Actions

The following table shows the attributes that are compared, when comparing workspace with repository user actions:

Attribute Comments

Comment - Specifies the comment of the user action.

Command - Specifies the command.

Run environment - Specifies the run environment of the command.

Prompt first - Specifies whether the command is prompted when the user action is invoked.

Refresh after - Specifies whether the selected resource is refreshed after the user action is invoked.

Show action - Specifies whether to show the user action when it applies.

Single selection - Specifies whether to show the user action only if a single object is selected.

Invoke once - Specifies whether the user action is invoked once for all selected objects.

File types - Specifies the file types the user action is assigned to.

Attribute		Comments
Comment	-	Specifies the comment of the user action.
Command	-	Specifies the command.
Run environment	-	Specifies the run environment of the command.
Prompt first	-	Specifies whether the command is prompted when the user action is invoked.
Refresh after	-	Specifies whether the selected resource is refreshed after the user action is invoked.
Show action	-	Specifies whether to show the user action when it applies.
Single selection	-	Specifies whether to show the user action only if a single object is selected.
Invoke once	-	Specifies whether the user action is invoked once for all selected objects.
File types	-	Specifies the file types the user action is assigned to.

Attributes Set When Adding User Actions

The following table shows the attributes that are set, when adding user actions to a system profile:

Attribute Comments

Label - Specifies the name of the user action.

Comment - Specifies the comment of the user action.

Command - Specifies the command.

Run environment - Specifies the run environment of the command.

Prompt first - Specifies whether the command is prompted when the user action is invoked.

Refresh after - Specifies whether the selected resource is refreshed after the user action is invoked.

Show action - Specifies whether to show the user action when it applies.

Single selection - Specifies whether to show the user action only if a single object is selected.

Invoke once - Specifies whether the user action is invoked once for all selected objects.

File types - Specifies the file types the user action is assigned to.

Order - Order of the user action.
Specifies the order of the user action, when selecting option 'User actions' from the context menu of a source member.

Vendor - Specifies the vendor of the user action. May not be used at all.

Attribute		Comments
Label	-	Specifies the name of the user action.
Comment	-	Specifies the comment of the user action.
Command	-	Specifies the command.
Run environment	-	Specifies the run environment of the command.
Prompt first	-	Specifies whether the command is prompted when the user action is invoked.
Refresh after	-	Specifies whether the selected resource is refreshed after the user action is invoked.
Show action	-	Specifies whether to show the user action when it applies.
Single selection	-	Specifies whether to show the user action only if a single object is selected.
Invoke once	-	Specifies whether the user action is invoked once for all selected objects.
File types	-	Specifies the file types the user action is assigned to.
Order	-	Order of the user action. Specifies the order of the user action, when selecting option 'User actions' from the context menu of a source member.
Vendor	-	Specifies the vendor of the user action. May not be used at all.

Not all beforehand mentioned properties can be maintained on the GUI.

Attributes Set When Updating User Actions

The following table shows the attributes that are updated, when updating user actions of a system profile:

Attribute Comments

Label - Not updated, because it is the identifying property.

Comment - Always updated.

Command - Always updated.

Run environment - Always updated.

Prompt first - Always updated.

Refresh after - Always updated.

Show action - Always updated.

Single selection - Always updated.

Invoke once - Always updated.

File types - Always updated.

Order - Always updated. Property is not available in WDSCi.

Vendor - Not changed on updates.

Attribute		Comments
Label	-	Not updated, because it is the identifying property.
Comment	-	Always updated.
Command	-	Always updated.
Run environment	-	Always updated.
Prompt first	-	Always updated.
Refresh after	-	Always updated.
Show action	-	Always updated.
Single selection	-	Always updated.
Invoke once	-	Always updated.
File types	-	Always updated.
Order	-	Always updated. Property is not available in WDSCi.
Vendor	-	Not changed on updates.

Restrictions

Note: User actions do not have an order attribute in WDSCi. Therefore user actions pushed to a WDSCi workspace cannot be added to the position stored in the XML file, but are added to the end of the list.