Martyn Houghton

@Steve Giller @Victor Thanks.

When chasing up change control, we create an activity for the user to undertake the change, which then expired after 24 hours before we email then again and create a new activity (thus triggering notifications/email etc). The activities show correctly on the Service Manager requests, but when you go into the main 'Activities' view you see both the current one and all the previous ones which are have expired. Should this not just display the current un-expired activities? Cheers Martyn

@Harry Hornbill Any update on this? Cheers Martyn

@David Hall I think we were getting confused by the Save button being enabled, however using the 'Add Translation' button we now get an error saying the translation already exists but it does not show on the screen when you open it. Cheers Martyn

@Adam Toms When viewing the service in the Employee Portal, do you get the 'Load More' button at the bottom? Cheers Martyn

@Steve Giller Emptying the cache and hard refresh has not resolved the issue. I have also proceeded to clear all browser data for all time and also tried in an incognito window, but still the translation does not save. Cheers Martyn

@Daniel I am sure @David Hallwill confirm, but it looks like the fixes include this weeks Service Manager Build, has reinstated this field and the sub status where this has been set using the old admin tool have been retained. Cheers Martyn

@David Hall I can confirm this has not been resolved by the Service Manager Build 2690, so can this be looked at. Cheers Martyn

@David Hall I can confirm this has been resolved by Service Manager build 2690. Cheers Martyn

Can we request that the API Scheduler for windows builds be extended so it is able to run natively as a Windows Service, rather than having to use a third party tool to get them to run as such. We want the API Scheduler to be running all the time and AutoStart when the server it is running on is restarted, i.e. following windows updates etc. Cheers Martyn

@SamS Thanks for confirming. Can the wiki be updated to reflect this as well. Cheers Martyn https://wiki.hornbill.com/index.php?title=API_keys

@David Hall Thanks, do we know what build number this will be? Cheers Martyn

@David Hall Thanks, do we know what build number this will be? Cheers Martyn

At the moment you can only create or updates service subscriptions using the 'SubscribeToServiceID" parameter with the Contact Import. Can we raise a enhancement request to add same option to the Organisation Importer as well, plus the ability to pass CatalogID to as exclusions as well. We are looking to migrate another Service Desk into our instances including all of their Organisations and want to import their subscriptions as well, rather than having to process them all manually. Cheers Martyn

When attempting to add a Translation to a Request Sub-status, they are not saved. My also be related to our other post where the Request Type for All is not pulled through. In this case I have to set the Request Type to All on the first tab before the Save button will enable. Cheers Martyn

When editing existing Request Sub-status which is set and shown as Request Type 'All' on the parent list screen in the admin tool, the Request Type is not carried through to the edit dialog window and requires manual population in order to save other changes. This could lead to the incorrect value being entered and also is unnecessary manual intervention. Can this please be populated with the current value. Cheers Martyn

You no longer seem to be able to create API Keys without specify an expiry date as a mandatory field, where as before this was optional. For ongoing live integrations we would not want to specify an expiry date. Cheers Martyn

Resolved this, as even though I set the 'bpmName' parameter to the correct display name of the BPM, the internal name used by Hornbill is all lower case with the spaces replaced with hyphens, so had to use 'idox-sr-slm' rather than 'Idox SR SLM'. Cheers Martyn

I am currently testing the creation of some reoccurring scheduled requests via the API Scheduler, but even though the requests get logged via the call to 'logServiceRequest' and the 'bpmName' parameter is passed with the correct and valid name, no BPM is being spawned against the request. Any suggestions as why it is not spawning? Cheers Martyn { "APIKey": "REMOVED", "InstanceID": "REMOVEd", "Schedule": [{ "Enabled": true, "CronSchedule": "15 * * * * *", "DayOfMonthANDDayOfWeek":false, "ScheduleFrom": "2022-07-25T00:00:00.000Z", "ScheduleTo": "2022-07-26T00:00:00.000Z", "Service": "apps/com.hornbill.servicemanager/ServiceRequests", "API": "logServiceRequest", "APIParams":{ "0": { "Type":"Content", "Parameter":"summary", "Content":"UKLive:- Prepare Detail Health Status report" }, "1": { "Type":"Content", "Parameter":"description", "Content":"# Check critical BI Jobs status\r\n# Check and verify the essential functionalities of Idox software solution\r\n# Take preventive action if any failure" }, "2": { "Type":"Content", "Parameter":"requestType", "Content":"Service Request" }, "3": { "Type":"Content", "Parameter":"customerId", "Content":"11152" }, "4": { "Type":"Content", "Parameter":"customerType", "Content":"1" }, "5": { "Type":"Content", "Parameter":"priorityId", "Content":"3" }, "6": { "Type":"Content", "Parameter":"sourceType", "Content":"Scheduler" }, "7": { "Type":"Content", "Parameter":"serviceId", "Content":"245" }, "8": { "Type":"Content", "Parameter":"catalogId", "Content":"973" }, "9": { "Type":"Content", "Parameter":"bpmName", "Content":"Idox SR SLM" } } }] }

Can we raise a request to have the option in the JSON configuration file for the API Schedule to control whether the 'Response Message' is appended into the log file as a whole, even better would be the option to specify the parameter(s) from the Response Message to insert into the log. Cheers Martyn

@Paul Alexander Thanks It try that with the logging from Post. I have also logged it with Hornbill Support as well. Cheers Martyn

@Paul Alexander I also seem to get the same behaviour when logging a request from a workspace post. Do you still have this when logging from an email? Cheers Martyn

+1 for us as well.

@Steve G Can you advise whether this option is now in the released API from Microsoft? Cheers Martyn

@samwoo Thanks, that works when you insert the operation within the last square bracket. You just get a warning on valididation of the workflow as it take the value as a literal variable reference. Cheers Martyn