Since initially making the Project Validation Rules available for download, I’ve seen it successfully incorporated into several sites. I’m now happy to post version 2 of this package which extends the core features originally described in the original post on December 4th, 2009.
Version 2 introduces the ability to validate information entered into pop up CDT windows. If you have already implemented the original version of this package and have not implemented your own extensions, you should be able to simply apply the new update and immediately take advantage of the ability to define rules for your Custom Data Types referenced by your Projects and Activities.
One of the challenges in adding support for rules that validate information in secondary and tertiary displays is how to effectively communicate that there is an error on a field that is not presented in the primary form. When editing project details within the project SmartForm, for example, the Hide/Show errors display needs to present the validation errors in a way that will lead the user to where the problem really is. This starts with the field or set on the SmartForm step itself. From there it also needs to give the user a breadcrumb of field names that they can follow which will ultimately lead to the field on the CDT popup form that needs to be corrected.
ProjectValidationRule 2.0 does just that but it doesn’t stop there. It also handles the case where that CDT form has fields on it that will also cause the popup of yet another window and so on. For this reason, the validation is now recursive.
I encourage you to read through the documentation to better understand how to take advantage of this package. You can download the latest version from my blog page on ClickCommerce.com.
Cheers!
Hi Tom,
ReplyDeleteI assume this is a typo, but I want to check. Are you NOT happy to post version 2?
"Since initially making the Project Validation Rules available for download, I’ve seen it successfully incorporated into several sites. I’m not happy to post version 2 of this package which extends the core features originally described in the original post on December 4th, 2009."
LOL - Yes, that was a typo. Now corrected. Thanks!
ReplyDelete