First of all Microsoft presented HTML 5 Self Service Portal (SSP) for SCSM almost year ago. There were 3 Updates released after that. Latest Update description has information about Enum List issue fix:
- Enums in list don’t appear in the same order as they are shown in the console.
I checked that issue with Out of Box lists (i.e. Incident Classification, Incident urgency…):
I changed Order in Incident Classification List and Add additional Entry in SCSM Console
After checked Enum List Order on SSP – but nothing changed in List Order or List Items
After I killed process and Entered SSP again Enum List for Incident Classification was in correct State
Main Idea if you expect to see changes for List Order on SSP as fast as possible you have to kill w3wp.exe process responsible for SSP Application in Task Manager on Internet Information Service (IIS) Server. This step described in MS Technet.
Next if you’re using Custom made Enum List for yours Applications, Offerings e.t.c and you develop management pack in Visual Studio/NotePad++ you probably will just Copy/Paste Entities and after that change IDs and you could face situation that in SCSM Console List will be in Correct order but on SSP it will be NOT same:
Cause of problem: same values in “Ordinal” Parameter for EnumerationValue.
Solution: make sure that you set Ordinal to appropriate values based on your List Order.
After that Items in yours List will appear in correct order.
THE USE OF THE WEBPAGES OF artempro.ru IS ON YOUR OWN RISK. THE INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, COURSE OF DEALING OR USAGE OF TRADE. artempro.ru IS NOT LIABLE FOR ANY WARRANTY CLAIMS OR DAMAGES, IRRESPECTIVE OF THE LEGAL CAUSE, WHETHER IN CONTRACT, WARRANTY, FAILURE OF A REMEDY TO ACHIEVE ITS INTENDED OR ESSENTIAL PURPOSES, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, INDEMNITY OR ANY OTHER LEGAL THEORY AND IN PARTICULAR SHALL NOT BE LIABLE FOR DAMAGES INCURRED AS A RESULT OF CONSULTATION, ASSISTANCE IN SETTING-UP PROCEDURES, BUSINESS INTERRUPTION OR SOFTWARE DEFECTS, EXCEPT WHERE LIABILITY IS MANDATORY FOR DAMAGES TO PRIVATELY USED PROPERTY OR BECAUSE OF VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS OR DUE TO INTENT, GROSS NEGLIGENCE OR FAILURE TO CONFORM TO EXPRESS WARRANTIES. HOWEVER, LIABILITY FOR DAMAGES ARISING FROM THE VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS SHALL BE LIMITED TO THE FORESEEABLE DAMAGE NORMALLY COVERED BY A CONTRACT EXCEPT IN CASES OF WILFUL MISCONDUCT OR GROSS NEGLIGENCE.