Martyn Houghton

@James Ainsworth Is there an update on the backlog change to allow catalog level subscriptions? Cheers Martyn

@James Ainsworth Thanks for the update. Cheers Martyn

@DeadMeatGF , @Victor, @DanielRi Apologies for resurrecting this issue thought apt on Halloween, but I am trying to achieve the same outcome without having to set up a dummy team just to clear an owner when trying to assign back to the same team with no owner. The other way I have managed to do this is by using the Assign to Service Team, which will clear the owner, but only works when the team you are working on is the first supporting team added to the service in question. I do think there the Assign Team BPM node needs to be enhanced to provide the ability to clear the current owner. Cheers Martyn

At the moment it seems you can only control the visibility of the reason entered when completing a Human Task using the system wide setting ' guest.ui.app.com.hornbill.servicemanager.operation.defaultVisibility'. Different services using the platform have different requirements on this, i.e. some want it to be shown others want to continue to be restricted. Can the option to set this on the BPM Node itself be added to the system, so the workflow itself set the visibility. Also if there was the ability to set the visibility default in the BPM Node but enable or disable the visibility selector to be displayed so the end user can override the default. Cheers Martyn

Where you have a large number of contacts set within an organisation for access via the customer portal, the current Portal Access screen can be somewhat of a pain to navigate and locate the account given that it does not appear to be sorted at all at the moment. Would it be possible to have the ability to filter on the portal access screen fields, as well as sort by contact name, 'Can Cancel' and 'Organisation View'. Thanks Martyn

It would be useful to be able to see and sort by a portal user's last login date/time in the Administration Tool. Would be of use in the contact view in the panel on the right-hand side where Logon Id is shown as well. Could this be looked at for a future release. Cheers Martyn

@Jenny We used to operate the same way and had the issue that analyst where sometime missing the 'New' incidents as they deliberately had to select the 'New' filter in the Request List to see them as there was not a default way to display only 'New' and 'Open' only on the Request List. We have now stopped using the parent status of 'New' and move to using s Sub-Status of 'New' under the parent status of 'Open' so that the requests are all in the same list. I would recommend looking at implementing Sub Statuses to see if this works for your implementation. Cheers Martyn

@SJEaton, @James Ainsworth This would be something we would also be interested in as well. I presume the calculation would also take into account the Working Time Calendar linked to the request via the current Service Level, so that it can take in to account Bank/Public Holidays as well as weekends? Cheers Martyn

@Giuseppe Iannacone The ServiceDeskDefaultCalendar has to remain and is used when you use the original SLA setup and is applied by default to all non SLM setup services where you use the Response/Resolution Timer. I believe the FeedbackCalendar is used to determine how long a user have the option to provide feedback on a closed request taking into account non-working days, bank holidays etc, but perhaps someone from Hornbill can confirm. In terms of question 3, the main concept you need to start is that Service Level Agreements and SLA's apply only to requests, not teams. Therefore the same is for Working Time Calendars, which you would be better thinking of as the hours the SLA operate rather than anything the links to the team working pattern. When you start a timer in the BPM with SLM setup, you do not specify a SLA, this is selected for you. The node will first apply the SLM rules set at the Service Level (i.e. only apply to this specific service) and then the rules at the SLA level (which apply to all Services link to the common SLA). Once these rules have been applied the request will be linked to a 'Service Level' within a 'Service Level Agreement', which also links to the working time calendar used in the calculation of the Response and Resolution targets. It does take a bit of getting used to, but it best to think about it about what are you committed to doing at a service level, rather than at a resource/people level. Hope this helps. Cheers Martyn

@Keith I see what you are trying to achieve in terms of having a hidden primary name which is perhaps numerical in nature, i.e. 001 Password Reset, which the list is sorted on but never displayed, as the display value is the Service Name. If current Service Name field was duplicated into a Service Display Name and the portal/live app changed to display this, but still sort by original service name field, I think this would allow you to achieve what you are wanting to do, without the need to all customers to set up ordering values straight away. Also if when setting up a new service the display valued defaults to the Service Name to save on having to re-enter it again if you do not need to order it initially. I presume you could sort of achieve this now by using a false translation of some kind, but that would be a pain to administer as well. I presume you are looking to group the services numerically in order to allow space for optional services to slot in that say a manager or team leaders may have? Cheers Martyn

Is it possible to restart/resume an SLA timer without resetting it? We have a situation where we stop the SLA timer as our 1st Tier has identified the customer has said the issue is resolved, but sometimes this is not correct, so we would want to put a secondary check in the workflow and if it is not correct route the workflow back to the investigation steps and restart/resume the timer. I know I could get around it by using a sub status under hold and not changing to resolved until double checked but wanted to know if it was possible to reverse the stopping the timer. Cheers Martyn

Not sure how sustainable/scalable manual ordering of service subscriptions would be, given that a coworker/contact could have services linked to them explicitly, as well as inherited from their team/organisation. The combinations could very quickly become enormous. Would it not be better to have certain standard order by options for the coworker/contact in the portal to have and for them to have the option set as their default order? I.e. order by name (both ascending and descending), number of active requests, number of request on hold, number of requests awaiting feedback etc. You could also then added a different tab similar to Favourites called Recent, which orders them by the order they last access the service via the portal, i.e. like your list of documents in Word when you open it? Cheers Martyn

This would be useful for use as well. Presume it would also work for raising linked requests for follow-on issues or where a user logs multiple issues on one request in the portal. Cheers Martyn

@Bob Dickinson, @Victor Are you able to shed any light on how the linkage of imported contacts is made to the parent organisation? I am wondering if the loader needs to be updated to include the additional step or newer API call to set up the relationship tables? Cheers Martyn

@mojahidm Okay Test 6 seems to be the most correct, but I suspect that the bit that is missing is the records in h_sys_org_contacts. Do you have a record in h_sys_org_contacts where the h_organization_id=14 and the h_contact_id=41? I thinking that the Organisation field in the contact display is calculated based on the relationship and not the actual value of h_company in the contact table. Cheers Martyn

@mojahidm Can you do a database direct query of the example contact record and post a screenshot of the values. SELECT h_pk_id,h_lastname,h_organization_id,h_company FROM h_sys_contact Cheers Martyn

@Giuseppe We are in the process of implementing different SLA's for a different customer using different Timezones/Working Time Calendars. You need to use the newer Service Level Management options, rather than the basic SLA option. https://wiki.hornbill.com/index.php/Structure_Service_Level_Management You can then assemble a SLA which relates to a Working Time Calendar and assign the SLA to a Service. A Service can have many SLA assigned to it and you use the rules at the Service Level to determine what SLA gets used when a request is logged for that service by a particular customer. In our case, we then use the rules at the SLA level to map what priority they have selected in the Progressive Capture/BPM to determine which 'Service Level' within the specific 'Service Level Agreement' to assign to the request when you start the timers in the BPM. You do not link the SLA to the teams, only the service and use the rule to map the service level based on the customer and other variable capture when the request is logged. Thereby each request has its own specific SLA/Service Level associated with it. Cheers Martyn

@ArmandoDM Thanks for moving this forward. Cheers Martyn

When loading bulk contacts you can specify the logon_id, but you cannot specify a contact's password or indicate if their guest portal account should be created and whether it should be Approved or Suspended. https://wiki.hornbill.com/index.php/SQL_Contact_Import Can the tool be extended to include these facilities, so it will make migrating customers from previous systems more seamless. Cheers Martyn

@mojahidm If you change the value you pass in the 'Company' field to the Organization_ID value, does it then link to the contact to the correct Organisation record? Cheers Martyn

There has been some movement on this on the recent SM builds, in that you can now view a 'Contacts' or 'Coworkers' service subscriptions. You cannot update them, but you can at least visualise them at this level, but not at Organisation or Department/Team levels. @Bob Dickinson is there anything in the pipeline to allow management of subscription from this angle. Cheers Martyn

@MikaP I did not think this is currently possible and is normally done by Hornbill as part of the Switch On Service. It is something we will need to do soon ourselves, as we are looking to add additional service desks onto our single instance. Hopefully, this is something that can be added like the Request Loader utility.Cheers Martyn

@SJEaton The 'Resolve By' column (not to be confused with the 'Resolved By' ) column should display the target resolution date and time if a Resolution SLA has been set and started on the request. The 'SLT' column will also give you the visual indication as well. Cheers Martyn

@Ehsan Phew! I was getting worried there. Cheers Martyn

@Ehsan Will this only affect cases raised between SM version 1073 and 1074, or will it affect all my active incidents present in the system when 1073 was applied? Cheers Martyn