Jump to content

Search the Community

Showing results for tags 'how to'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Hornbill Platform and Applications
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Service Manager
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Configuration 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 4 results

  1. When configuring SLA response and resolution targets and expiry times on certain BP nodes you might find the target being set differently than possibly expected. This is because a common oversight as these timers needs to be expressed in SLC (Service Level Calendar) times or working hours or business hours (which are usually X hours/day) rather than calendar time (which is 24 hrs/day). When configuring a target time of N days, the value needed to be set would be N working days rather than N calendar days. The value that needs to be set will be obtained by multiplying N with the number of working or business hours/day. We advise to always configure hours (rather than days) as it is easier to figure out the values required to be configured for SLA targets or expiry times on business process nodes. However, in certain areas (e.g. SLA timers), depending on the target, it might not be always possible to use hours exclusively. Below is a quick example of how to find out which values needs to be configured depending on the intended target: Let's say we need to configure a resolution time (or an expiry time) of 5 days. We need the target to be set in 5 days from now. Let's also say the working hours are 7.5 hours/day although this really depends on your SLC. Step 1 is to find out the number of working hours equal to the 5 days we need to set: 5 days * 7.5 hrs/day = 37.5 hours. You need to configure round values therefore if you don't have a round number of hours you also need minutes (seconds, etc.). The 37.5 hours equates to 37 hrs and 30 min. In conclusion, for a 5 day target, the configuration needs to be 37 hrs and 30 min. As mentioned above, for simplicity always use hours if possible. If you need to configure this value as days/hours/min then the 37.5 hours need to be divided by 24 (which is the number of calendar hours in a day) resulting in 37.5 / 24 = 1.56 days. The 1.56 days equates to 1 day and 13.50 hours. This further equates to 1 day 13 hours and 30 min. In conclusion: 5 day target in the context of 7.5 working hours/day is set as: 37 hours and 30 minutes or 1 day 13 hours and 30 min If you don't want to be bothered with the mathematical calculation, you can use this Excel sheet to find out what values you need to configure. Type in the desired target time and the number of working hours per day. The values you need to configure are in red: Hornbill_Timer_Targets.xlsx IMPORTANT: the above does not apply when configuring expiry times on human tasks. Human tasks do not account for Working Time Calendar and as such the above setup does not apply in this scenario.
  2. When building a report using the SQL Schema Designer, you might find that you are unable to configure custom column headers. This functionality can be enabled and made available if you configure table aliases for the table(s) used in the report (https://wiki.hornbill.com/index.php/Table/Column_Alias)Note: This does not apply when building reports using Entity or Measure. Custom column header functionality is available in this case.
  3. Hi all, Is there a way to only reference working days, say when placing a job on hold for a set time. Thanks
  4. Hi, We've just created multiple Teams within our IT (we just had everyone in one before) and Management now want us to assign calls to Teams rather than individuals. Up until now Analysts received email notifications letting them know when a call had been assigned to them - this worked well. I have now had to turn on the TeamEmailAssignment setting and setup an appropriate email template so everyone in the team knows there is a call that needs picking up. This in itself isn't an issue - what is however, is that as part of every BP a call is assigned to our 1st Line (1st node in the process) to be reviewed and dealt with or assigned on as appropriate - this is meaning that the 1st line (who are constantly monitoring the incoming calls) are also getting emails to let them know a call has come in. I can see now way to exclude them from this as it's a global setting so I would like to ask the following: Is there any way of setting a default team for calls to automatically be assigned to so that they don't receive the Team email? Or Is there another way someone has managed to get round this? I only set this up this morning and it's already driving them mad! FYI - I can't filter it based on service as all our teams support each service. Thanks Tina
×
×
  • Create New...