0 votes

I am upgrading to version 2013-2 and I have found an issue with default field values. I'm hoping you can assist me with this.

“Web Filtering Level” is associated with extensionattribute4:

Note that the default value is not populated in the field:

Note that the field property pattern is recognized:

Also note that one of the custom fields hints data bleeds into the field value.

by (950 points)
0

I emailed the web configuration backup file.

It appears (included in my email) that one of my regular expressions is causing the issue. I noted other odd behavior that is corrected when this is removed in the email.

I do get an error in IE. Here are the details:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; vul-na)
Timestamp: Mon, 16 Dec 2013 19:40:16 UTC

Message: Syntax error in regular expression
Line: 1
Char: 19032
Code: 0
URI: https://jaxadproxy.na.vul.com/AdaxesAdm ... idators.js

Message: Syntax error in regular expression
Line: 1
Char: 19032
Code: 0
URI: https://jaxadproxy.na.vul.com/AdaxesAdm ... idators.js

0

Hello,

It is very likely that the issue is caused by the regular expression. The thing is that both checking of the values against regular expressions and setting default values for properties are handled by JavaScript. So, if the regular expression is incorrect and failing, this can also prevent the JavaScript from performing the other functions correctly.

Right now our QA guys are checking the issue to make sure that it is only the regular expression that is causing the issue. If the issue is in the regular expression, we will help you to build a correct one.

0

Thank you very much for your prompt attention to this. I appreciate it.

0

The issue is caused by the highlighted part of the regular expression that cannot be parsed:
^(?i)[a-z0-9_.%\-]+@([a-z0-9_\-]+\.)+[a-z0-9_\-]+$

What is it supposed to check for?

0

In some regex syntax, this ignores the case.

1 Answer

0 votes
by (215k points)

Such syntax is not supported.

You can use the default regex provided by Adaxes for the Email property that does exactly the same:
^[a-zA-Z0-9_.%\-]+@([a-zA-Z0-9_\-]+\.)+[a-zA-Z0-9_\-]+$
Instead of using some syntax to ignore the case, it simply adds uppercase characters as an allowed character class.

Related questions

0 votes
1 answer

We have a New User action set up for our HR staff to use. There is a field in the custom form that states "Notes for IT Department". I want to display the data that is ... IT Helpdesk. I don't know what parameter this would be considered. How can I find out?

asked Feb 14, 2020 by slowllama (100 points)
0 votes
1 answer

Dear Support, Is it possible in "generate default value" section of pattern for multivalued attribute to provide more than 1 value from "must be one of" section? E.g. Pattern ... E" and to have default generated values in web interface "A,C" Thanks for advise!

asked Jul 7, 2020 by Dmytro.Rudyi (850 points)
0 votes
1 answer

We are trying to enforce better consistency for user attribute values in a domain but without overly restricting user input when modifying/creating users. Is it possible to ... to these fields and create Custom Commands to change them which is very tedious.

asked Mar 21, 2019 by Staj (350 points)
0 votes
1 answer

Hi, I am trying to setup a Home Page action in the Help Desk portal to modify a User account, for this i want to specify the default value of a property to be the ... the user account i am modifying to get the default value? Thanks in advance for any help!

asked Dec 1, 2016 by sam.webster (320 points)
0 votes
1 answer

We have a form to used by our HR Reps to create non-employee records. There are two fields on the form that are auto-generated via a property pattern: Full Name ( ... changed to cause this new behavior? Nothing has changed with our property pattern set-up...

asked Aug 30, 2016 by sandramnc (790 points)
2,740 questions
2,474 answers
6,475 comments
1,372,117 users