Jump to content

NickH

Hornbill Users
  • Posts

    35
  • Joined

  • Last visited

Everything posted by NickH

  1. Update :- Managed to invoke the workflow (needed to port the service selected in the parent change into the new change). However I've hit a new snag, that when the parent change was created during the progressive capture stage the requester selects an individual that they want a certain authorisation task to be assigned to, however when the duplicated change gets to that step in the workflow it understandable falls down. Is there a way of taking the PC questions with the duplicated change? I've tried mapping the user selected in the PC to a custom field, copying that into the new change and then using that to drive who the task is assigned to, but it doesn't work, I guess because it's the handle you select at the PC stage but HB needs to know the ID when assigning a task?
  2. Thanks Daniel, I like this idea, and have set up as per your helpful instructions, however although a new Change record is created it (understandably) doesn't invoke the same workflow that brand new changes do. I.e. our Change workflow has a number of tasks that get fired out as the record moves through it's lifecycle. I feel like I'm missing a piece of the puzzle on how to make the duplicated change follow that same workflow. Thanks again Nick
  3. Thanks both, gives me something to make a start with.
  4. Hi all, We've just on-boarded to HB and are currently testing our Change workflow before go live. During some demo's a couple of uses have noted our current (and very basic) system has the ability to create a new Change from one that already exists, i.e. it copies the details into a new one, at which point the requester can change any of the minor differing details - I.e. the software version in the description. Can any more experienced users highlight how they do this, or how you might go about it please? Many thanks Nick
  5. Morning all, Is there a way of changing the 'no reply' prefix on e-mails that have been auto generated by the system, i.e. those that contain an authorisiation task? I was hoping the following setting would do it, but changing it doesn't seem to have made any difference. Many thanks Nick
  6. Thanks Steven, That all worked, much appreciated! Nick
  7. Thanks for the swift reply Steven, I'll give this a go.
  8. Morning all, I suspect this is an easy one! I want to ping an email out once a change is authorised, I've set up a template with all the relevant details populated, except one. I can't find a variable that relates to the dates entered using the built in 'schedule' calendar? Should this be possible? Many thanks Nick
  9. Afternoon all, The owner of our change process has raised a point that users aren't allowed to raise changes that span more then 'x' amount of days or are 'x' amount of days in the future. I.e users shouldn't be able to raise a change 3 months down the line that lasts for 5 days. I don't think we can presently put any constraints around the schedule (?) but can we request a feature be added so we can help our workflow confirm to our internal Change Process? Thanks! Nick
  10. Firstly apologies if this isn't in the correct section. As part of our progressive capture questions for raising a new change, we ask the user to input the start and end times. The start/end times are currently individual questions on 1 customized form. Is there a way of making a relationship between the start time and end time, with the end goal of having some validation so that the user can't put an end time in that is before the start time? Many thanks Nick
×
×
  • Create New...