Jump to content

Search the Community

Showing results for tags 'timeline update'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Organisation


Location


Interests


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 3 results

  1. We have seen a change in behaviour which I can't explain, we have a human task defined in a business process which used to create a timeline entry: This is no longer appearing when the same task is processed. The business process hasn't been published since October 2020 and I can't find any settings that can explain this change - the above example where the timeline WAS written to is from 29th April, today this is no loner working. A human task node just before this one is still creating a timeline entry: The 'Has the Date/Time changed?' node is writing to the timeline as expected, and the 'New Change Time Selection' node is not, this is the relevant part of the business process: The 'New Change Time Selection' node is using a single Outcome with 2 fields: Fields: And I've tried taking a copy of the business process and adding a new node to manually update the timeline, this is also not working, I've tried with visibility set to 'team' and 'public': Is anybody else having issues with timeline updates? Is this the result of a release? (we were updated to build 2223 19/05/2021 @ 01:01:40) Thanks, Luke
  2. Can I raise an enhancement request to the Notification Bell list to make it more powerful and allow you to preview the notification before having to click on it which then dismisses the notification. Often we will have many notifications about updates on requests but with the limited information available in the Notification Bell list it is not easier to determine there priority without opening them which then removes them from the list so if it is not a priority you have got to remember to go back to it. If hovering over the request reference could pop out the request summary dialog as it does on the Request List screen, this would allow us to remind us of the request context. Then if hovering over the first time element it provided a preview of the timeline/workspace post the notification is linked you would be able to determine whether you need to action the notification now or leave it in your list to pickup later. Example mock up below. Cheers Martyn
  3. At the moment in most BPM nodes you have the ability to determine if the timeline is updated or not. What would be useful is for these options to be expanded to include the visibility of the timeline update, i.e. have the option No, Yes and Yes (Team only). Cheers Martyn
×
×
  • Create New...