Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/11/2021 in all areas

  1. Hello everyone, The latest update of Hornbill Core UI (1502) has been released to live. The change log for this update is as follows: New Employee Portal - New widget config: Use Content Height - If checked, the widget expands to height of the contents or to the tallest widget in the same row. I might have a maximum height limit.Fix Employee Portal - Bulletins Widget - Was showing wrong height when used in a row in the middleApps List - Collaboration description was wrongEmployee Portal - Bulletin Widget - "Show More" not positioned correctlyConversations - Unable to see scrollbars when opening a big imageEmployee Portal - Footer Text is only returning text from the primary company - https://community.hornbill.com/topic/21253-employee-portal-about-details-maybe-bug/
    1 point
  2. Hi @Tina.Lapere, Here is an example (sorry for the ugly colours) where the 1st and 3rd has the flag turned ON. You can see that the first widget has a lot of content and therefore it will expand. Since the last one has the flag ON, it will expand to match the 1st one. But the 2nd one does not have the flag and it stays the same. I think it will work for you either way you want to display it. If you want all the widgets to have the same height, flag all of them in that row. Regards, Daniel.
    1 point
  3. @Kelvin @Mike Hillman Just an update that the patch has just been deployed... sometimes it can take a few mins to be noticeable with caching etc but the issue should now be resolved... if you can keep and eye on it this afternoon and let me know how it goes. Kind Regards, Dave
    1 point
  4. Hi @Adrian Simpkins Something that you may want to consider is building this into your BPM workflow on a request. This way you wont need to adjust any of your rights or roles. As part of a "Resolution Stage" you could have options after a request is either Resolved or Closed where you have a suspend operation that is waiting for some form of update to the request which will instigate the automatic re-opening of the request. Possibly a task to for owner of the request to confirm with the customer that the resolution has worked. Rather than just letting someone re-open a request for any old reason, you can provide more control with the circumstances that a request can be re-opened. It is common practice to only re-open requests that have been recently closed. You could use an expiry so that after a few days the suspend node ends and that request can no longer be re-opened and a new request needs to be raised. Regards, James
    1 point
×
×
  • Create New...