I requested it as proposed. The ID is PMPER-1117. Hope the text is understandeable.
We're creating own actions by separating the code from the configuration, whereas promptsets are being used to pass the configuration to the code.
In example we have a housekeeping action - object that we reuse in many places spread over various applications. We configure the action on the task level on the promptset. To distinguish the uses of the housekeeping-object, we set alias names on the tasks. So if the user refer's to "object A" he's likely to refer to an "alias A within workflow C which makes use of (action)object B".
The issue we have now is, that users are searching for "their housekeeping object named A" as they don't realize, that "A" is a virtual name for their usage of the globally available object B within their workflow. So people are telling us, that their "object B" has not been deployed as they have issues understanding the concept. Also we have then to do "workaround search-for-use"-searches to find the approptiate task the client refers to.
My request is, that the global search should also integrate and highlight alias-names. There might be a special icon indicating that the search did not find an object but an alias (or alike).
Retrieving data ...