Application aliases
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2024 01:32 PM
Hello! I know we can't be the only organization where people refer to applications with different names. For example, we have a 'Central Licensing System' that some call 'CLS' and others call 'Central Licensing'. It's in APM as 'Central Licensing System' but then when people want to search on 'CLS' they won't find it. That's a simple example. There are others with multiple names. The obvious answer is to just tell people to use the formal name we have established in APM. Not so sure how practical that is... 🙂 Before we moved APM into ServiceNow, we had people add some text to the description to list the aliases. For example: For application "Mark's Cool App" they might include "Alias: MCA" in the description - and then could search the description field for "Alias: MCA" to find it.
Is there a best practice for ServiceNow APM to handle aliases like this?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2024 07:17 AM
Hi, maybe you can use tags to acheieve it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2024 06:55 AM
Hi Doron! Thanks for the idea. Definitely something for me to consider. Would that be preferred to adding a custom field? I've been contemplating a text field where people could list the various aliases that are used and then we could use that to do "contains" searches to find the apps...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2024 10:37 AM
Using a custom field will work as well
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2024 10:46 AM
Thanks. Is there one approach - tags vs. custom field - that would be considered "best practice"?