ArmandoDM

Hi @LouiseT can you please double check the value of this app-setting api.xmlmc.queryExec.maxResultsAllowed, just to exclude this as a possible reason you can only export 11 Thank you Armando

Hi @LouiseT can you please clarify, is the number of assets you see in the list greater than the number of assets exported, or the filter applied to the list only returns 11 assets and you expect more ? Regards Armando

Hi @Josh Bridgens the issue you reported has been accepted as a defect and a fix will be provided in one of the upcoming builds. Regards Armando

Hi @Josh Bridgens is there any FAQs active for the service? If not, may you please add one and try again? Regards Armando

Hi @yelyah.nodrog as @Martyn Houghton suggests you cannot add elements to the picklist, but you may rename them. In this thread there are more details on how to rename them. Hope this helps Armando

@John C I will mention to the relevant people about this. Regards Armando

@John C you may add new values to the asset substates. To do this, you need to go in the Asset Type page and click the icon top right of the page Thank you Armando

Hi @John C as @Victor said, State and Operation State cannot be edited. Regards Armando

Hi @Ann we cannot replicate this issue. Can you please clear the browser cache, reload the page and try again? Which browser are you using? Did you double check that the asset Substates are still defined ? Regards Armando

Hi @ALIPO by the look of the screenshot it looks like the view has already been created, the screenshot is for a view already existing. The button SAVE will be disabled until you change some conditions on the filter and/or the filter name. I suppose he has changed something before hitting the SAVE button ?

Hi @ALIPO may you please post a screenshot of what the conditions in the view look like? Ideally we would like to replicate the issue for investigation Regards Armando

Hi @Frank Reay thank you for the clarification, it was my misunderstanding, I thought it was the csv upload function via the App screen. I will mention the issue to the relevant team, to see if there is a way to achieve what requested. Regards Armando

Hi @Francis von Stein the issue has been addressed and it will be available with the next build. The size of Device ID will be 64 characters. Regards Armando

Hi @Izu importing the assets via CSV is only used to add assets, not update them. So, if you add an asset and do not populate the relevant properties for Used By/Owned By then these values will be left as NULL. Regards Armando

Hi @Francis von Stein we will increase the length to 60 characters to meet your needs. Regards Armando

Hi @Paul Alexander the issue has been fixed and it will be available with the next build. Regards Armando

Hi @Paul Alexander the error you see is because the subscriber ID of the CI you're trying to exclude is longer than 64 characters. I will report this issue for fix, the maximum allowable size for h_subscriber_id needs to be increased. In the meantime, if you would like to hide the CI for some users, you may subscribe them personally to the service and then hide from the CI. Apologies for the inconvenience. Regards Armando

Hi @yelyah.nodrog the action focus just tells which tab, in the request page, will be open when a user open the request. It can be anything, this will not affect the functionality of the BPM node. As your BPM is suspended waiting to be resolved, you may set Action focus to 'Resolve'. Hope this helps Armando

@Jamie Talbot yes it seems correct. Make sure that the suspend node is put just before the decision node in your BPM process

Hi @Paul Lear do you know how many bulletins the service has ? The issue is caused by incorrect data into the table h_itsm_service_bulletins. For some bulletins without image, the value h_service_bulletin_image is not empty as it should be. If you can verify the content of this table and blank h_service_bulletin_image for the bulletins without image , this should fix the issue. If you can do the above and confirm that the issue is fixed it would be great. I will report this issue for fix. Apologies for any inconvenience Regards Armando

Hi @Jamie Talbot the value Stage Expired will be set to true/false , you may use these values in your decision node. Regards Armando

Hi @Nikolaj the new build should be available this week, not too sure the exact day. Regards Armando

Hi @Paul Alexander not sure why it took so long, but glad to hear that's sorted now. Regards Armando

Hi @Paul Alexander the same issue has already been fixed in the past, so I suspect you're displayed a cached value. May I ask you trying to remove/add the Get request information node and see if the issue is fixed ? This is the thread where the same issue was reported a while ago Thank you Armando

Hi @Nikolaj yes, the issue has been fixed and it will be available with the next build. Thank you Armando