Jump to content

Search the Community

Showing results for tags 'Historic Updates'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Hornbill Platform and Applications
    • OpenForWork
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • IT Operations Management
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start








Website URL





Found 5 results

  1. I am currently undertaking test migrations using the SQL Request Importer (v1.3.1), and I am trying to carry over a much information into the Historic Updates that the tool allows. Would it be possible to get some clarification on the below:- h_updatedby and h_updategroup, are these just literal values or are there lookups applied to them such as the User lookup and Team Mapping? h_actiontype and h_actionsource I am presuming these are textual literal values which we can pass in any text from the source system? h_timespent is passed in as an integer in the unit of minutes? Cheers Martyn
  2. We are approaching 6 months of using Service Manager live having migrated from Support Works. However my analyst are still logging into Support Works to use the search facility to locate historic requests and previous occurrences of issues. Though we have migrated a proportion of our previous request, the global Request Search does not search the content of the 'Historic Updates' linked to the request, therefore you can not locate references to the issue being searched for in either closed historic request or active requests transferred over. Can the indexer component linked to the global request being modified to include the historic updates as this will mean analyst no longer need to log into Support Works to find previous occurrences of the issue. Cheers Martyn
  3. When the Historic Update section is populated by Request Loader tool, i.e. transferring from Support Works, the updates are displayed in oldest first order and there is no option as there is under timeline to alter the order. Is it possible for a change request to be raised to have the ability to order Historic Updates in the same way as the Timeline, plus the same default applied display order to be the same on both? Cheers Martyn
  4. When Historic Updates are created via the Request Loader tool, each update record has the View Attachment link associated with it, even if there are no attachments. Would it be possible to have a count of the attachments next to link or the link disabled/removed when there is not any present? Cheers Martyn
  5. We are using the Request Cleaner tool to clear down requests created/loaded as part of our testing. Having previously loaded historic updates from Support Works, including attachments, I have run the tool this morning to clear down all requests. Checking my disk usage on the instance via the admin tool the space taken up by loading of the Historic Update Attachments does not appear to have been released. Is there a time delay between cleaning down the requests and the linked attachments being removed? Cheers Martyn
  • Create New...