Jump to content

James Ainsworth

Hornbill Product Specialists
  • Posts

    4,940
  • Joined

  • Last visited

  • Days Won

    277

Posts posted by James Ainsworth

  1. Hi @Art at BU

    This is a translation button.  It has been detected that the language that the notice was written in is different from the language set in the user's profile.  I believe that there may be an issue between US and UK English.

    The translation button will be displayed if the notice was written in US English, but the user's profile is set to UK English.  As they are both English, the Google translation doesn't do anything when you click on the button.

    I believe that the development team is already aware of this and have it in their queue to look at.  

    • Thanks 1
  2. Hi @Sandip Bhogal

    Thanks for your post.

    The field names are key here when including this information in the email.  You will see that the answer to the question What date should access be removed? is stored in field_2

    image.png

     

    Looking at the Authorisation Details, I can't quite see it but it looks like the Department is using field_2, and the Type of access is field_1.  I'm not 100% sure but it might be that these fields need to be aligned with the correct field names.  Difficult without having access to the capture and workflow to say exactly what's happening.  

    image.png

  3. Hi @Cigdem Turner

    Thanks for your post.

    As the site is being saved in the Custom_o field you will need to retrieve that information just before the decision node where you check which site name has been added.  This will be one of the Get Request Information tasks.  You will then use the result of that Get Information in the Custom Expression.  It is also best practice to include a branch for No Match just in case something goes wrong and there isn't a match with the two sites.

     

    1. Get Request Information

    image.png

    2. Custom Expression for Facilities Vista

    image.png

    3. Custom Expression for Facilities Melbourne

    image.png

    Let us know if that helps or if you need more info to get this set up.

  4. Hi @Llyr

    In the BPM there are some string utilities. There isn't a single one that on its own would go and strip out all special characters.  However, there may be a combination of these that may be able to do some of this.

    image.png

     

    I've done a test using the Replace Task with the settings below which successfully removed an apostrophe from the middle of a string.  This is limited to only being able to test for one character at a time, but if you know which character is causing the most issues, this should help.

    image.png

    1. Use a Get Information automation to read in the surname from where you have it stored.
    2. Use the variable that holds the surname and add it to the Input Text.
    3. Add the character that you want to remove in the Search String field
    4. Set the Replace With to Manual and don't add any value to the field
    5. Have another Hornbill Automation that takes the result of the Replace automation and update the request with the new value.

    Let me know if that helps or if you need more information to set this up.

  5. Try adding the Board's role Board BPM Access to the users that update requests that have Board Automations in the workflow.

    In some cases, it may be necessary to give this role to all.  For example, if there are customers that use the Employee Portal and their interaction with a request might trigger a board update, this would ensure that the rights are available for the automation to take place.

    https://wiki.hornbill.com/index.php?title=Board_Manager_Administration#Roles

  6. Hi @Llyr

    Thanks for your post.  In some places, validation can be added to control what is initially entered into a field.  There are also some string utilities that can be used in a workflow that could be used.  However, I probably need a bit more information about the scenario that you are looking at.  Is there a particular field that you are looking at and how is this field currently being populated?

  7. Hi @AnthonyUSS

    I'd probably need to know a little bit more about your configuration.  There is some documentation on this topic.

    https://wiki.hornbill.com/index.php?title=Escalation_Actions

    The one thing to keep an eye open for is the hours specified in the Working Time Calendar.  Escalation events will use the Working Time Calendar to calculate escalations.  For example, 24 hours can equal 3 days if your Working Time Calendar is set to 8-hour days.

     

  8. The resolve button doesn't actually let them resolve the request.  This tab appears when a resolution has been provided and it is just a way for the end user to confirm if the resolution has worked.  This is normal for a 2 stage closure process where confirmation of the fix is provided by the customer before closing.  If you don't wish to show this, you could add an automation in your workflow to close the request as soon as it is resolved.

    image.png

  9. Hi @TWoodford

    Thanks for your post.

    The starting point is to look at your list of Views to see if any of these have a chart defined. 

    image.png

     

    If you are looking for charts that are provided in a Shared View, you will need to make the charts visible.  Charts that are included in a Shared View do not automatically get added to the My Dashboard.  They must be made visible by clicking on the cog icon and then the icon to make them visible.  

     

    image.png

     

    image.png

  10. Hi @WFMKC

    On 8/18/2023 at 3:10 AM, WFMKC said:

    I wonder, is it possibly linked to this?

    Possibly, but the KE00167283 was raised almost a year ago, so if this has only started being an issue for you since the 19th of July, there's a chance that something else might be causing it.  This KE is also referring to the Suspend->Await Expiry and your question is on the Suspend->Wait for Request Off Hold.

     

  11. Hi @Estie

    I believe I have gotten to the bottom of the issue. These first two highlighted forms are forms that are never seen by a user on the employee portal.  This is because we already know who the user is and the service that is associated with the capture.  This means that by the time the first branch is reached, there has yet been a form that is available to display to the user on the portal.  

     

    image.png

     

    When the flow goes down the path of Student the cancel form comes immediately after.  This means that there has never been a form available to display to the user.  When the capture flow tries to add the Cancel button there is no form to add it to which results in the lines.   This is why it worked for me when I put in a custom form between the Student branch and the cancel.

    The No Match will work as it is always displaying the HR or SITs Managed form.

    So the end result is that somewhere between the Start and the Cancel there must be at least one form that has been presented to the user.

    I hope that helps.

     

     

    • Like 1
×
×
  • Create New...