0
Completed

Allow for customizable operation names

Bob Bradley 7 years ago • updated by anonymous 4 years ago 8

When configuring a multi-step operation list involving more than one PowerShell Script operation there is no quick way of differentiating between each operation (e.g. if you are moving them up and down). A solution would be to create a new operation name property which could be (optionally) set on the Operation Detail page.

Tony,

If you can remember enough about this, is this something that could easily be achieved between a v3.0.2b and v3.0.2 RTM, or is it complicated enough that it requires v3.0.3 or v3.1?

This could be easily achieved; simply updating the OperationConfigurationInformationBase to require a DisplayName shows this.

It would be a good idea to make all operations easier to distinguish apart. If this is going to be too difficult for some operations, consider instead adding an operation comment, much like the operation list comment.

As pointed out in EB-520, the display names are displayed as null if not defined.

The mechanism is in place on the service, and all UI components have been updated to support this. Only part remaining is to work out the cleanest way to ensure that updated MA names are updated in EB, this might be as simple as refreshing the calculated names following a call to Refresh the FIM Agent MAs.

Default calculation should be reverted to studio side for un-customized operation names.

Reassigned for confirmation of completion.

Confirmed in latest installation.