Keith Posted September 4, 2017 Share Posted September 4, 2017 When trying to create a view using sub status the sub status description is corrupt. See below. Link to comment Share on other sites More sharing options...
David Hall Posted September 4, 2017 Share Posted September 4, 2017 Hi Keith, The icons should be there, they have been added to show you the service icon, followed by the request type icon and then finally whether it is a running or paused sub-state... however for some reason you are missing the name of the sub-status which should be being shown before the final icon. I'll see if I can replicate the issue locally. Regards, Dave. Link to comment Share on other sites More sharing options...
Keith Posted September 4, 2017 Author Share Posted September 4, 2017 Thanks for the quick response @David Hall 1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted September 4, 2017 Share Posted September 4, 2017 @Keith Have you just applied Service Manager 1048 by any chance? Cheers Martyn Link to comment Share on other sites More sharing options...
Keith Posted September 4, 2017 Author Share Posted September 4, 2017 @Martyn Houghton Yep, and was trying to test out the ability to have sub status in views. Link to comment Share on other sites More sharing options...
Martyn Houghton Posted September 4, 2017 Share Posted September 4, 2017 @Keith Thanks, that what was waiting for as well. Cheers Martyn Link to comment Share on other sites More sharing options...
David Hall Posted September 4, 2017 Share Posted September 4, 2017 @Keith At a quick glance it looks like its something do do with the list not being able to find the sub-status string in your selected language or a suitable default language string, I've managed to replicate when switching language so when I get the bottom of it I'll post up. Regards, Dave. Link to comment Share on other sites More sharing options...
David Hall Posted September 4, 2017 Share Posted September 4, 2017 @Keith I've identified the issue, apologies but there was a incorrect parameter being used when trying to use the default translation string for the sub-status entries in the selection list. Could you confirm that your selected session language is different to the language used for the sub-statuses? If this is the case then this would result in you falling back to the default string which is unfortunately not displayed due to the parameter issue. I'll raise a problem record for this and get the fix put in now. As a short-term workaround, if the sub-statuses have all been created under a different language to your current language setting, you could try temporarily switching your session language from the top right profile icon to that used in the sub-statuses, this should then show the translation text. Or alternatively you could also add a translation entry into each sub-status for the language that you are using. If you have any queries on this just ask. Regards, Dave. Link to comment Share on other sites More sharing options...
David Hall Posted September 4, 2017 Share Posted September 4, 2017 @Keith We're just working on an update for this and another defect, so there should be a new release of SM shortly which will include a fix for this. Regards, Dave. Link to comment Share on other sites More sharing options...
Keith Posted September 4, 2017 Author Share Posted September 4, 2017 @David Hall Thanks for investigating. The language I am logged in on is actually the same as that which the sub status' are maintained in (English - British). However my profile has a blank entry for language, so not sure if that could be causing the issue. Either way I look forward to the fix being worked on. Keith Link to comment Share on other sites More sharing options...
David Hall Posted September 4, 2017 Share Posted September 4, 2017 @Keith Oh ok, yeah thats an odd one for it to be missing from the profile, but quite likely to be the issue. I have a fix completed, so as soon as we are able we will release an update with it included. Regards Dave, Link to comment Share on other sites More sharing options...
David Hall Posted September 5, 2017 Share Posted September 5, 2017 @Keith Just FYI we released an update this morning (1049) which should include the fix for this issue, for some reason it has not shown in the release notes but it was included. If you still have any issues after the update then just let me know. Regards, Dave. Link to comment Share on other sites More sharing options...
Keith Posted September 6, 2017 Author Share Posted September 6, 2017 Thanks @David Hall I'll let you know if we have any further issues with it. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now