Idea Details

Personalize views

Last activity 06-13-2019 09:52 AM
Anon Anon's profile image
04-01-2011 09:49 AM

Ability to personalize list views by selecting columns you would like exported after a search.   Submitted on behalf of the FL CA Service Management User Group.


Comments

12-21-2017 07:40 AM

Our company would very much like to see this implemented.  It should be available from every list form.  Most of your competitors have this functionality already.

06-15-2017 04:16 AM

I have strong interest in this idea from a client who has just implemented r17.  It could reduce the need to create form groups and multiple versions of list forms for different job roles and/or tenants.

01-12-2017 01:49 PM

While xFlow (14.1.03) delivered some degree of personalization (e.g. ability for analysts to create their own work streams), there are several items on this thread that have not been delivered and are not included with the planned work for release 17. Because of this and the high level of interest in this idea, I am changing the stage to "wish-listed" for consideration in our future planning sessions.

08-26-2016 08:11 AM

Hello All,

The power of users (analyst and teh desk in our case) would be that we have less request to build reports in BO. Analysts have the search to create the conditions and when tehy can change the columns shown they can export the result and work from there or work in SDM when needed. Analysts have visibillity in the tool so no extra authourisation is required. You don't want to deliver this to end users that logged a call or request.

08-25-2016 09:47 PM

Hi J W,

 

Dale is not able to respond.   But if he was talking about within the ITSM 14 web client, then this feature hasn't been included.

 

You could use xFlow - it's good for many things like this. But I don't know if that if that is what the original idea or Dale's reply was about.

 

Kyle_R.

08-25-2016 01:38 PM

Was this Delivered as part of xFlow?

 

J.W.

03-11-2016 03:22 PM

Please make sure that we have a security layer there as some info may have been intentionally hidden on the ticket level and you don't  want to generate a backdoor by viewing them in the list having the user managing those columns himself.

So must be an attributes of the field that allow display or not in list that admin can manage

/J

12-14-2015 02:51 AM

Personalized views will ower the pressure on BO reporting.

Let people drag their own attributes in a view and run a search. Worked perfect in a former product we used.

12-08-2015 11:49 AM

Unfortunately, this capability was not included in the 14.1 release. The 14.1 version still uses definitions from the Web Screen Painter and the forms groups to control which columns appear for the Analyst role.


This is one of the elements that we are considering as part of the Analyst User Experience design that we unveiled at CA World and are working towards for an upcoming release.  

08-17-2015 09:33 PM

I will vote for your idea

04-12-2015 08:05 PM

Is this in ITSM 14.1?

 

Kyle_R.

01-27-2014 01:31 PM

This is currently planned as part of the new SDM 13.0.

07-18-2013 12:09 AM

This would be very useful.  Also better control over the list view, similar to what we had previously which is now gone and replaced with the expandable lists that can not be properly controlled.

12-08-2011 03:43 AM

Similar kind of ability is added in the CA Service Catalog, where administrator can add/remove columns that are visible to the user

04-12-2011 02:21 PM

An analyst type user should have the ability to modify the columns displayed, and ultimately exported, in a particular object list. For example if a level 1 user is looking at an incident list screen they can see the incident number, summary, priority and affected end user. But for their job role the user wants to see the attached CI for the incident. The user can easily see a list of columns to add/remove and reorder from their list view and modify as they see fit and save it. All of this user&#39;s future incident list views will show their defined list and order of columns. This should be preserved when patches or upgrades are done.<br>