Thanks for your answers. Because it's technically heavy to configure and for the reasons you have explains (breaking the logic, have to made a CA...), I'll not implement it. Have a nice day.

Hello there, I'm encountering a problem. For a customer, I have to made a specific action on a RCDC submission. On a creation (or modification) RCDC form, I have a date binded attribute. For a submission request, I want to check if the date submitted is superior than actual date. For exemple, this field could be used for the date of a depart of a collaborator. The point is that in the windows of a binding configuration of a date attribute, there's not validation tab. And so, I can't do a verification on it. However, there's a regex field on the extended attribute tab. But it seems that we can't use it for testing a regular expression based on a date. And so my questions are : - Is it possible to do a verification on a date attribute ? With a special trick ? - Is there some date variable in FIM portal that we can use on a regular expresion ? Thanks. Best regards.

Julien - haven't got any good news sorry ... search for "date picker" here and you will see that there is no built-in control capability, and nor can you "roll your own" in this version of FIM. About the best you can do is write a custom activity to run in an AuthZ workflow such that an exception is raised if the date is invalid - this will fail the request, but you will have to start data entry all over again I'm afraid. Also, if you mean something like "today's date" in FIM, there is only really a temporal set definition that comes close to this - but not really sure what you mean by "use on a regular expression". Perhaps you giving an example would help?Bob Bradley, www.unifysolutions.net (FIMBob?)

That's a very nice idea. But how to mandate the String value is greater than, basically, System.DateTime.UtcNow? Unfortunately the only way I can see you can accomplish this is via AuthZ like Bob says.

yup as I said if and only if the validation is fixed (like you only need valid format for a date, or a fixed range), if some variable factor like "greater than today" exists you cannot use RegEx. even if you could use the current date and calculate the format of the regular expression and fill the "StringRegex" dynamically in the BindingDescription or AttributeDescription object in FIM, and have some service or script to process that daily. you don't want to miss with validation based on [today] parameter, since that will break the logic; when ever you open an old resource to update other fields, it will fail to let you save changes if date field is not valid even if its not changed. as u know its client-side validation (javascript) that will block submit if validation failed for the whole page. so when dealing with variable factor I agree that the best choice is to use an Authz activity since you can configure it to run only if the date value is changed using R-MPR.

beside what bob has specified, if your validation is fixed based on regular expression why not to use an initial string attribute and have validation on it, for example create "dateString" configured with your regular expression based on date format "MM/dd/yyyy" doing regular expression with dates is annoying when range is a factor: 01/01/2010 -> 12/31/2011 ^(0[1-9]|1[012])/(0[1-9]|[12]\d|3[01])/201(0|1)$ then you can create an MPR when the "dateString" is added or modified, and use the function evaluator as: - use the function dateTimeFormat(dateString,"yyyy-MM-ddTHH:mm:ss.000") and assign it to date-type attribute to be used in other logics.