65 results found

1. Customize spell check and dictionary

   Need to be able to add custom applications and new words to the dictionary and spell checker

   36 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →

2. make it simple to compare two database fields in GlideAggregate and GlideRecord queries.

   Example: Just today I wanted to be able to compare the date that an incident was due to the date that the incident was actually completed (to determine how many incidents were completed on time).

   Currently, in order to accomplish this I have to do one of two things -- I can either grab all the incidents and loop through them comparing them in javascript -- or I can create a new field on the table to store the value, create a business rule to fill this value on insert/update, and run a background script to populate past values.

   Could/should work like:

   gr.addQuery('fieldOne', '>=', 'fieldTwo');

   Example: Just today I wanted to be able to compare the date that an incident was due to the date that the incident was actually completed (to determine how many incidents were completed on time).

   Currently, in order to accomplish this I have to do one of two things -- I can either grab all the incidents and loop through them comparing them in javascript -- or I can create a new field on the table to store the value, create a business rule to fill this value on insert/update, and run a background script to populate past values.

   Could/should… more

   31 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   planned  ·  AdminMatt Beran (Admin, ServiceNow) responded

   I’m setting the status of this to “planned”

3. Rich text and html support for fields and journals (comments, work notes etc)

   Allow rich text and HTML formatting to be added to Comments and worknotes to feed journalled fields to enable retention of formatting, inline images etc on log creation from forms, emails etc. Although there are 'solutions' for doing this, they are currently unsupported by SN support and implemented at the customers risk. Plain text in the 21st century really isn't good enough!

   30 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →

4. Printing a workflow

   I would like an option to print workflows or to export them to MS Visio

   30 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  Delete…  ·  Admin →
   planned  ·  AdminMatt Beran (Admin, ServiceNow) responded

   This is coming soon.

5. allow to modify cookie's expiry date

   By default, if you use the 'remember me' functionality, the cookie stored in your pc is set to expire in 2078. There's not cookie manager in the system or property to change it. Since we use LDAP authentication, this is not effective. We want the users to re-authenticate after their password has expired.

   24 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →

6. Allow perma and pretty Links for all incidents, knowledge, changes, etc.

   I can no longer justify sending links that look like this to the CEO:
   https://DEMO.service-now.com/sys_attachment.do?sys_id=8fcb35c60a0a3c1c017cd77b61309ec8&sysparm_viewer_table=kb_knowledge&sysparm_viewer_id=8fc8c91f0a0a3c1c0149bc22d14c4848

   22 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   7 comments  ·  Delete…  ·  Admin →

7. resizing of columns in list

   Allow resizing of columns in list view "a-la-Excel" style. Whilst we are on the subject, why not the row resize too!

   21 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →

8. New/enhanced catalog variable types

   A number of new or enhanced service catalog variable types would be really useful for us (and I hope others):

   For reference fields, add AJAXTableCompleter functionality. (It's really infuriating that we can do this in, say, Incident's caller field but not in a reference type catalog variable. Use case: you try finding the user you want out of our nearly 80000 many of whom have duplicated names).

   Also for reference catalog variables the ability to use the tree_picker functionality that we can already use on a regular form would be great. Use case: selecting a department from our tree of 470-ish.

   Last but not least, how about a list collector variable that shows not a plain list but a tree picker on the left hand side? e.g. selecting a set of department references.

   A number of new or enhanced service catalog variable types would be really useful for us (and I hope others):

   For reference fields, add AJAXTableCompleter functionality. (It's really infuriating that we can do this in, say, Incident's caller field but not in a reference type catalog variable. Use case: you try finding the user you want out of our nearly 80000 many of whom have duplicated names).

   Also for reference catalog variables the ability to use the tree_picker functionality that we can already use on a regular form would be great. Use case: selecting a department from our tree of… more

   20 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →

9. Knowledge Management: Post Articles to multiple topics

   • Overview: Knowledge articles often may be logically categorized into multiple topics / categories. By restricting the selection to a single topic / category, we reduce the chances of articles being found via browsing. Also, in many cases, we wish to “highlight” articles in News even though the article actually belongs in a specific topic or category. If we post multiple copies, we multiply the work required if we need to update the articles and increase the chance of the copies getting out of sync and providing conflicting information.
   • For example, we have a news article on what to do if users encounter issues with Service-now while using the application. We’ve got this posted in News currently, but would also like to have it posted in Service-now / Support.
   • Suggestion: I can see 2 alternatives that could work:
   o Allow multiple Topic / Category selections to be made when posting articles. Ideally, we should be able to not have a limit on the number of selections, but could manage with 1-2 alternate posting topic / category selections.
   
   o Have a flag on articles to say that they should also appear in “News” and allow a “Publish to” and “Valid to” date for the news separately. Possibly also a News Short description also.
    Example: News Article: “Service-now Release 24 – Changes and Updates.” Base Article – publish on 3/20/2010. Valid to 3/20/2011. Topic / Category – Service-now / Release Notes. News Flag – checked. Publish from / to – 3/18/2010 – 3/25/1010. News Short Description: “Service-now – Maintenance / Update Alert – Release 24 – 3/20/2010 – 12:00 AM”
   • End Result: We can highlight news items but still maintain “findability” of information in their natural topics / categories. Articles will not have to have multiple copies floating about, reducing the complexity of updates to multiple copies.

   • Overview: Knowledge articles often may be logically categorized into multiple topics / categories. By restricting the selection to a single topic / category, we reduce the chances of articles being found via browsing. Also, in many cases, we wish to “highlight” articles in News even though the article actually belongs in a specific topic or category. If we post multiple copies, we multiply the work required if we need to update the articles and increase the chance of the copies getting out of sync and providing conflicting information.
   • For example, we have a news article on what to… more

   19 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →

10. Add TinyUrl(URL shortening) support for Firefox and Chrome as well.

    URL shortening is currently supported only for IE. Recently I faced the issue of records not opening because the URL generated is prettly big in Firefox and Chrome. It is not happening in IE because URL shortening is supported for IE.

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →

11. Allow standard SQL syntax to populate a GlideRecord (incl. joins, group by, case-when, subqueries, table variables, etc.)

    Developers with experience querying relational databases using SQL can tell you that pulling and joining data is far easier using SQL syntax than using a Web GUI (fine for beginners but very slow and tedious compared to typing a query for those who know SQL) or having to define the query with Glide commands in code (very limited compared to SQL, ie no joins, cross-tab, etc.)

    When googling around to see if it was possible I came across the gs.sql command, which seems to be an unofficial way to query ServiceNow with SQL-like syntax, for example
    gs.sql("select count(*) from incident");

    However, it is undocumented and what little I found had warnings about it being "dangerous" and unsupported.

    I'm not sure how ServiceNow's underlying data engine is implemented - although the data appears to be standard tables like in a regular relational DB, the core system may not be implemented using traditional SQL. Also it is understandable that giving all the users unlimited access to SQL commands can wreak havoc from a support standpoint. By abstracting away the physical database, SN avoids (and helps their customers avoid) a lot of pitfalls you can run into with traditional relational databases.

    That said, it would just be VERY helpful if we could populate GlideRecords using standard SQL syntax (including joins, cross-tabs, sub-queries, and at least the basic commands you get in MS T-SQL or Oracle PL/SQL).

    I'm not asking SN to re-invent their database implementation, just provide a layer that "emulates" SQL so that we programmers used to SQL have more powerful and familiar tools to work with our data.

    A couple of sample use cases would be joining tables in a certain way, populating a GlideRecord with a crosstab query (pivot table), more easily transform data inside a script for whatever it needs.

    Supporting SQL syntax would go hand-in-hand with the suggestion for ODBC support from external applications. That way a standard SQL query could be written and re-used from inside ServiceNow or an external application.

    Note: we have been able to query our ServiceNow data from SQL Server Management Studio using a linked database and openquery, however this is very limited. In order to fully access the data from a SQL environment, it is necessary to create a view for each table, pulling each field as string data and casting it as the specific data type. We have had a lot of issues such as timeouts with large data sets, truncation of long fields, etc. Standardized ODBC would make life a lot easier.

    Developers with experience querying relational databases using SQL can tell you that pulling and joining data is far easier using SQL syntax than using a Web GUI (fine for beginners but very slow and tedious compared to typing a query for those who know SQL) or having to define the query with Glide commands in code (very limited compared to SQL, ie no joins, cross-tab, etc.)

    When googling around to see if it was possible I came across the gs.sql command, which seems to be an unofficial way to query ServiceNow with SQL-like syntax, for example
    gs.sql("select count(*) from incident");

    … more

    14 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →

12. Meaningful BSM Maps

    Enhance the BSM Map functionality so that relationships can visually show more meaning. For instance, if there is a relationship of 'sends data to' then display the line in the BSM map as a different format or color (should be customizable).

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →

13. Allow requesters to choose from cart which request(s) they want to submit.

    Currently, when any request is submitted, all requests in cart are also submitted, even if they are not complete.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →

14. Support MS Office 2010

    I would like to export directly to a .xlsx file and make imports from Project 2010 to ServiceNow.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Delete…  ·  Admin →

15. Add the ability to designate specific tables and columns as "report" tables/columns

    Right now the Report Editor allows users to select any table and any column on that table. In reality, there are really only a handful of tables and on those tables, only a limited set of columns that are really needed for reporting. Many tables and columns are used for system purposes. By allowing this designation, it would provide a simpler interface to anyone writing reports.

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →

16. Allow group by to also have a criteria

    When using group by I would like to also say do not show records with count >=1.

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →

17. Create feeds off of tables (RSS and iCal)

    Can you imagine you have you're email client synced up with service-now's rss for incidents and you see em that way additionally if the calendars had an ical format most email clients can import that as a calendar and would change with it.

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    started  ·  1 comment  ·  Delete…  ·  Admin →

18. allow users to create their own cubes for reporting escpecially for custom tables

    It's hard to create cubes or pivot table with only preset list of tables, This will be useful for custom tables .

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →

19. XML syntax highlighting

    The Javascript Editor plugin was an awesome enhancement for helping to keep you in the tool while developing/writing scripts. I think a great improvement along these same lines would be to offer the same type of solution for the XML fields throughout the system (UI Pages, Macros, etc.)

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →

20. Allow for Outlook MSG file support

    Currently when an outlook MSG file is sent into Service-Now from an email it corrupts and becomes unreadable. Would be great if this format was supported.

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Delete…  ·  Admin →