Jump to content

Conor

Hornbill Product Specialists
  • Content Count

    118
  • Joined

  • Last visited

  • Days Won

    6

Conor last won the day on January 29

Conor had the most liked content!

Community Reputation

35 Excellent

1 Follower

About Conor

  • Rank
    Product Specialist

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,214 profile views
  1. @aykut.boyraz The routing rule expressions are essentially SQL statements so the easiest way to meet your requirement would be to add to your existing expression something like: AND fromAddress NOT LIKE '%@BlockedDomain.com' Obviously replacing BlockedDomain.com with the domain you want to block. You could use the fromDomain instead, I recommend trying it out to see what works best for you
  2. @Ann-MarieHolloway I couldn't tell you if there will ever be an option, with the rolling roadmap things change fequently so it is certainly possible. As far as I am aware there is nothing planned at the moment though. @Steven Boardman @James Ainsworth have either of you heard anything about this potential enhancement?
  3. Hi @Ann-MarieHolloway There isn't currently a way to add a comment using the FAQ functionality. You could use the customer feedback part to ask questions related to the FAQs, but these won't be linked directly to the FAQs as this customer feedback will require a request logged and resolved first. There is a way to report on the user and their feedback per FAQ though, and that information is held in the h_itsm_faqs_feedback table. You can use the reporting suite or Advanced Analytics in the admin portal, but not the in-app reporting. The data will show you the FAQ that feedback was given for, the user that gave the feedback, and the rating - which is either 1 for thumbs up, or 0 for thumbs down. Hope this helps
  4. Hi @Jeremy You can add in a custom field to cater for this. On the Co-worker profile page in the analyst portal click the design button at the top (just above first name): Add in a custom field called title, and then you can populate it directly from the import using the relevant custom field, i.e. attrib1.
  5. You would have to put it in one of the existing fields yes. Why there isn't a specific field for the prefix I don't know, but as far as I'm aware you are the first to ask about it...
  6. Hi @Jeremy Yes absolutely - the only hesitation I would have is whether or not the prefixes are in the source data, if they are then from this page it says: It is possible to construct a value by specifing multiple directory attributes against a Hornbill user property E.g.: * "Handle":"[givenName] [sn]", - Both Variables are evaluated from LDAP and set to the Handle (name) param So you can simply add the strings together in the import as above, or alternatively put the prefix into one of the unused fields on the user profile. If the prefix value is not in the source data, then you can hardcode it in to an import, but as it's hard coded every user imported will have that same prefix so you would have to create multiple imports Thanks Conor
  7. Hi @AndyHodkinsonPrincesIT It looks like the issue may be because you are using the old import tool - try the new one in the admin portal here: Home > System > Data > Data Import Configurations. It's all the same fields with a few extra functions, but managed within the admin portal. Further info here: https://wiki.hornbill.com/index.php/LDAP_User_Import The Timezone is a drop down firstly, although the currency symbol is still free text, but I can confirm that the euro symbol does work from the user interface and the value is stored in the DB... if that helps... Try it from the new import tool and let us know how you get on
  8. Hi @Alisha For most types of posts you can change the visibility in the individual update. As far as I'm aware customer updates and system updates you cannot change visibility... (someone feel free to correct me if I'm wrong) but all others you can simply click on the 3 dots in the bottom right of the update -> select the change visbility option -> set to the correct value
  9. @SJEaton is the call class switched on at the top? I've done this myself...
  10. Hi @Lyonel I have spoken to the development team who have now raised a change to add this in to any of the view builder options that may be missing the 'is not' filter. They have added this post in as a reference so you will be notified as soon as it is available. Thanks Conor
  11. Hi @Lyonel I cannot see the image in your post I'm afraid, however most of the filters on the view builder that I have checked do have an 'is not' option. Which one are you looking at in particular?
  12. Hi @Jack Tuckwell In terms of a test environment I suggest talking to your relationship manager at care@hornbill.com who will be able to provide any details about this, however based on your post I don't think it is necessary. In terms of issues with the import, using our Hornbill cleaner you can clear down all asset data easily. If this is an initial attempt at importing assets and for any reason you want to try again, run the hornbill cleaner utility from here: https://wiki.hornbill.com/index.php/Hornbill_Clean_Utility and this will clear down all asset data. Please read the full configuration detail as this could also clear down request data if not configured properly. Also remember to reset the asset ID counter as detailed on the wiki page, otherwise the next asset import you run will start as the auto ID after the last one finished - this is a relatively minor point but worth bearing in mind. The asset import may appear daunting on an initial glance but it is really quite straight forward in practise. I suggest giving it a try and let us know if you encounter any issues or have any questions. Lansweeper can tie in very nicely to the custom buttons functionality against an asset record too, so at a click on the asset record you can quickly see the finer details of each asset in a lansweeper view. I believe some detail on this is about to be published on the wiki, although it is very straight forward again so let us know if it's not there yet and you need any help with this. Thanks Conor
  13. Yes @Dan Munns Both will have the filter field to set up the above so yes this applies to both old and new import scripts. You can filter on any value within LDAP, and the filter syntax is standard LDAP syntax, which is something like: (&(objectClass=person)(objectClass=user)) - for AND (|(objectClass=person)(objectClass=user)) - for OR (&(objectClass=group)(&(ou:dn:=Chicago)(!(ou:dn:=Wrigleyville)))) - for NOT
  14. Hi @Dan Munns I would simply create two imports, one that only selects the users with the relevant value in attribute 1, and then another for everyone else. You can set up as many imports as you want to, and this method will keep it simple to set up and manage. Using the filter in the ldap import, for the full users import add the filter ad attribute 1 = xyz, and then in the basic user import exclude the users where the ad attribute 1 = xyz. Then in each import script everyone that is selected will have the user value set, and everyone else will have the basic user value set. That will do it!
  15. @Aaron Summers no problem! I have also added you in as a connection to the above mentioned change, and just in case others would also be interested in this feature I've added a link to this forum post within the change. Anybody else - let us know of your interest here, and we will notify everyone that has expressed an interest when the change has been released.
×
×
  • Create New...