We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Allow Custom Classes to Display in the Portal
Brett_Moffett
Cireson PACE Super IT Monkey ✭✭✭✭✭
When extending SCSM with a custom class it is not currently possible to expose this new class within the Cireson portal.
Allowing a custom class to be synced via the CacheBuilder and then able to be displayed using a custom written form would allow administrators to further extend the functionality of the Cireson portal in alignment with their SCSM console.
A settings screen that would be accessible by administrators on the portal could expose a list of classes to sync to the ServiceManagement DB.
Once synced to the ServiceManagement DB, a new form could be created by copying the Incident.js (or other similar template) and renamed to the class name and edited to contain the class properties formatted in the same way other forms are currently displayed.
The base view navigation page could be created using a Saved Search to create the initial grid of items. Only once these are clicked on would it expose the related form.
Eventually, a for designer would assist in creating these forms but for this feature a manual creation of the form would suffice.
PROS:
CONS:
Allowing a custom class to be synced via the CacheBuilder and then able to be displayed using a custom written form would allow administrators to further extend the functionality of the Cireson portal in alignment with their SCSM console.
A settings screen that would be accessible by administrators on the portal could expose a list of classes to sync to the ServiceManagement DB.
Once synced to the ServiceManagement DB, a new form could be created by copying the Incident.js (or other similar template) and renamed to the class name and edited to contain the class properties formatted in the same way other forms are currently displayed.
The base view navigation page could be created using a Saved Search to create the initial grid of items. Only once these are clicked on would it expose the related form.
Eventually, a for designer would assist in creating these forms but for this feature a manual creation of the form would suffice.
PROS:
- Closer Alignment of SCSM Console and Cireson Portal experience for extended environments
- Further extension of data collected by ServiceManagement DB to assist with faster reporting and long term storage of data in Analytics.
CONS:
- ServiceManagement DB size could grow fast if not managed correctly
- Manual form design could be difficult to manage and deliver correctly to end user
32
Comments
This needs all the votes we collectively have, IMHO. Telling my users the equivalent of "ignore the ad-hoc search, what you really need is an SSRS report against the warehouse for every conceivable permutation of searches you would want to perform, even though you'll throw it away and need something different after one use" is getting very old for me.
Literally when I was just about to click "Post Comment," someone else just stopped into my office asking why the search doesn't work, and why they can't add other fields like Description to the results. People are finally realizing the potential usefulness of all the data we are collecting about our processes and starting to have a look at it without any prompting, only to find out that they can't do the simplest searches with it. It is a momentum-killer and its effects are getting worse, not better.
While I am told and understand to some extent that it might be a high-effort endeavor to fix this, to me it is like a 200yr old single-lane bridge on an interstate (warning: imperfect metaphor ahead!). Infrastructure projects do not draw the ooh's and ah's, and nobody wants to take one lane down to zero for an extended period of time, but everyone is going to ask why you didn't do something about it sooner when the bridge collapses from disrepair, or else they are going to be happy with your interstate after it is not only stable but now has a proper two lanes--and they will forget about the inconvenience, later on. I have said this before, but this should be the best feature of the system, but instead it is the worst. Please invest the time and effort necessary to turn it around. I think @Brett_Moffett's FR above lays the framework for this, expertly (not sure if his intention included Work Item Search or not, but I interpret it that way).
@Brett_Moffett - Any status update?
SQL ServiceManager Class Properties and Relationships - CIRESON SENPAI NOTICE ME!