Jump to content

Ehsan

Hornbill Developer
  • Content Count

    517
  • Joined

  • Last visited

  • Days Won

    19

Ehsan last won the day on April 2

Ehsan had the most liked content!

Community Reputation

74 Excellent

1 Follower

About Ehsan

  • Rank
    Senior Member

Profile Information

  • Gender
    Male
  • Location
    South Ruislip, London

Recent Profile Visitors

1,238 profile views
  1. Hi @chriscorcoran, Thank you for bringing this to our attention. We have identified the cause and this will be addressed in the next Hornbill Collaboration build; please look out for the next Hornbill Collaboration build in the Announcements section. FYI, square brackets in the Wiki are used to format a date & time value based on your Profile's Regional Settings. Please refer to "Date Formatting" section below: https://wiki.hornbill.com/index.php/Wiki_Markup Thanks, Ehsan
  2. Hi @Martyn Houghton, I have added code to enable the Phone Action for Change Requests. This will be available towards the end of this month. Ehsan
  3. @Martyn Houghton, I have added alphabetical order to the Category drop-down list. This will be available towards the end of this month. Thanks, Ehsan
  4. Hi @SJEaton, The development team have added code to wiki markup to cater for the DATETIME value that is returned by custom22 and other DATETIME fields. In the next Hornbill Collaboration build, if you wrap the value in custom22 in square brackets, it should show in the UI as your Profile's format. As below: [&[global["outputParams"]["custom22"]]] Thanks, Ehsan
  5. @Martyn Houghton, The styling in the Customer Portal is supplied by Hornbill, hence the font is hard-coded to a default value. I'm not sure if you could redirect the styling as it's delivered via a framework compiled file. Ehsan
  6. Hi @Martyn Houghton, Unfortunately it is currently not possible to change the font in the Customer Portal. As we're continuing to grow the Employee Portal and carrying out some major work to refresh the Portals, there will be no enhancements to this area until further notice. Thanks, Ehsan
  7. Hello Everyone, The latest build of Hornbill Service Manager (1480) has been released to live. Change Log for this release are as follows: New New operation called 'Entity > Requests > Update Request > First Time Fix' to set a Request's First Time Fix following it's resolution based on configured conditions. Please refer to 'First Time Fix' bullet list in this Wiki page for more details -https://wiki.hornbill.com/index.php/Service_Manager_Business_Process_Workflow#Update_Request.{CH00120464} New reports added to 'Satisfaction' category in Service Manager's Reports module to help analyse Customer Feedback and ratings. Please refer to this Wiki page for details on enabling Service Manager Reports - https://wiki.hornbill.com/index.php/Service_Manager_Experimental_Features#Service_Manager_Reports.{CH00128897} You can now subscribe sub-groups of a subscribed organisation to a Service. This can be enabled through 'com.hornbill.servicemanager.services.subscriptions.allowSubgroupsInclusion' setting. Please refer to this Wiki page for more details - https://wiki.hornbill.com/index.php/Subscribers#Subscribing_Sub-Groups. {CH00141945} You can now export the list in the Assets view. Please refer to 'Export Assets' bullet list in this Wiki page for more details - https://wiki.hornbill.com/index.php/Manage_Assets#Asset_List. {CH00153931} You can now configure Service Level escalations to post Hornbill notifications. Please refer to this Wiki page for more details - https://wiki.hornbill.com/index.php/Escalation_Actions. {CH00144902} Changes Improvements to the time picker when placing a Request on-hold. {CH00155360} Provided paging on the Asset form in Progressive Capture. Please refer to this Wiki page for details on Progressive Capture forms - https://wiki.hornbill.com/index.php/Progressive_Capture_Workflow. {CH00154461} Fix Error when the BPM attempts to assign a Request to a team that was updated at the same time. {PM00154834} Authorisation action does not open automatically when highlighted by the business process. {PM00155027} Service subscriber id field is smaller than the allowed id for system group entries. {PM00155095} 'Wait for Status Change' BPM operation does not return a Request's status when stage has expired. {PM00155125} Long titles and content can exceed form width in a Request's Questions section. {PM00155277} Request list fails to format Custom fields 21-30. {PM00155312} Date picker question answers display a day early for users west of GMT. {PM00155294}
  8. Hi @Logan Graham, Sorry I should've mentioned! You'll need to enable the Post types that are permitted to be edited, via guest.servicemanager.request.timeline.availablePostTypes.editPost application setting. In the example below, I've only chosen "Update", meaning that only posts with that type can be edited.
  9. Hi @Logan Graham, @Jeremy, You can't delete a Timeline entry as this is considered as a change in history. You can however edit your own post, using the Edit Post option. I can also edit my own comment, using the Edit option. If you're an administrator on your instance (i.e. Assigned the Super User Role or Admin Role), you'll be able to edit another person's post or comment. This will be audited for security purposes. I hope this helps. Ehsan
  10. @SJEaton Home icon > My Profile sub-menu... As below;
  11. @Paul Alexander - The issue in relation to Custom Fields in Tasks presenting ab un-formatted Date Time value on selection - This has been accepted as a defect by our development team. @SJEaton, we also looked into the issue that you mentioned here. It will require further investigation, we will get back to you as soon as I have more update on this.
  12. @Paul Alexander Yep, it is a separate problem but has the same root cause. I have asked the team internally about both those issues.
  13. @SJEaton @Paul Alexander, As this was bugging me (I knew I had it working somehow...), I looked into it again this morning and here's some concrete findings... I have a Progressive Capture that is associated to a Catalog. Within the Progressive Capture, I have a custom form... And a field within the custom form. Please note that the Field ID is startDateTime and the Field Type is Date & Time control. In my Business Process, I have added Entity > Requests > Get Request Information > Progressive Capture Answers automated task. This step is crucial in my findings. In my Human Task, I have used the Variable Picker to locate my field and Inject the variable into the Task details section as below... The injected variable looks like below... I had to wrap the injected variable in between brackets [ ]. I then went on to change my Date Time Format to below. I had previously missed this part - You have to logout and login again for this to take effect. I then went on to raise a Request against my Catalog and prompted to select a Date Time in my custom form. When viewing the task, my preferred Date Time Format is correctly applied. The above is scenario in which Date Time Format will be correctly applied. Here's a scenario where the Date Time Format won't be applied and I believe this is what you're doing @SJEaton, So you have a field in your Request details where you capture Date Time. e.g. "Expected Delivery Date" in the example below. It doesn't actually matter where you're capturing it from - The important note is that it's being saved into h_custom_22 column. In your Process, Entity > Requests > Get Request Information > Request Details automated task returns the Request data and you've used the Variable Picker to inject a value as below. And when viewing the task, it looks like... So I can replicate it. I can see why that is - The raw value is stored against the task, hence the timezone information is missed. I will need to speak to the team internally to understand what can be done here.
  14. Hi @Dan Munns, This was rectified in a Service Manager build that went Live this morning. Please update to this build. In the Profiles configuration, the Name Separator was blank and since then, the server enforced this property. This went unnoticed and we've rectified this in the server (to apply a default separator of ->) and through Service Manager, to update all default Profiles to include a Name Separator (if none existed before). Thanks
  15. @SJEaton Yes that's right, I can't see no other way of showing a date/time based on user's preference in tasks.
×
×
  • Create New...