Jump to content

Search the Community

Showing results for tags 'regex'.

  • 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
    • Employee Portal
    • Service Manager
    • IT Operations Management
    • 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 7 results

  1. I am trying to use RegEx validation to restrict the length of a field to 30 characters, but having issues with the RegEx criteria. ^.{1,30} Testing it in the Progressive Capture Editor and in submitting a request, it is not stopping the user from entering more than 30 characters. Anyone can clarify where I going wrong with the RegEx expression? Cheers Martyn
  2. Hi I would like to restrict the text users can enter so it's in the format S####, eg S0005. Is this possible? Thanks
  3. In lines with my previous post of being able to add customer descriptions to the standard Request Details node in progressive capture, it would also be useful to be able to apply validation using same Regex options as you can do on custom forms. From our point of view we are wanting to restrict certain characters and also the length of the summary field, as we use this value in operations latter which include appending other references/values. Cheers Martyn
  4. I am trying to use the pre Import Actions within the Data import configuration section to modify several attributes being imported from AD. AD Attribute "StreetAddress" needs to be mapped to Hornbill site value. Currently "streetAddress" contains carriage returns which need to be removed so lookup can match to a site location. AD Attribute "Department" needs to be mapped to Hornbill Department and Sub-Department value. Currently "Department" is in the format Department : Sub-department and needs to be split on the colon so lookup can match everything before colon to department and
  5. Hey All, Quick Question, We have a field in our Progressive capture with H_Summary as a field ID in it, to pull information into our summary on the request list page. I have made it a Single line text field but people are putting too much information into the field which is stopping it from pulling the information up to the summary. If their a code we can put in the Regex Field to control the amount of characters that can be put in? Like when you can specify it to only have numbers input? Like above? Many Thanks Hayley.
  6. Hi all, I am having difficulty getting the email rules to work this morning. We have changed mailboxes and as such I need to create a rule as follows: "If email is sent from <old address> and contains subject line <IT Request Form 2016> logOrUpdateServiceRequest" However I cannot get the email rules to play ball today. Any help gratefully received Thanks Dan
  7. Hi , I am trying to set up a custom form in our progessive capture and having issues with the regex validation . I am trying to capture a phonenumber and only allow 11 digits as input. i tried this syntax REGEX_MATCH(Phonenumber,'[0-9]{11}') but it does not work , i always get a <false> i have attached a screeshot of the field settings . Any idea where I am going wrong ? Thanks Ralf
×
×
  • Create New...