After a loooong BETA period, and quite a few modification to DFFS and the plugins, I’m finally ready with a new production release.
There are a few nice additions like better backup / restore functionality with support for creating restore points, and new loader functionality that lets you load different DFFS versions side by side in the same site. This way you can do a gradual upgrade of DFFS – one form at the time.
Please read the full change log to see all changes. You find the change log here: http://spjsblog.com/dffs/dffs-change-log/
Follow the download link here to get the new package.
Please note that the user manual hasn’t been updated yet, but I’ll do my best to update the manual within a few days.
Please post questions in the appropriate forum: http://spjsblog.com/forums/
I have uploaded a new BETA version of DFFS and plugins.
I’m sorry for the long delay from the previous BETA, and that I cannot give you a production ready release.
Based on feedback from the previous BETA I had to do some changes to how multichoice field triggers was handled, and this turned out to be a bit more complicated than I first anticipated.
When I was at it, I ended up doing quite a bit more work to enhance the DFFS backend experience – with for example better version control and backup and restore functionality.
Read the change log and get the DFFS-package here, and please post any feedback in the forum.
I have updated CommentBox for SharePoint to add support for auto-subscribe to replies on your new comments.
See change log for a bit more details.
Please post any feedback in the forum.
I also want to say thanks for my award as one of the “Top 50 Sharepoint Blogs and Websites for SharePoint Administrators, Architects, Developers and Business users” by linking back to http://blog.feedspot.com/Sharepoint_blogs/
I have released v22.214.171.124 of the SPJS Charts for SharePoint solution. There is only two small changes in this release. I have removed an alert in the code that prevented the use of jQuery v2.x, and fixed an issue with drilldown when no items was found in the drilldown result.
I have spent a lot of time last week and in the weekend trying to sort out some problems with “on-change rules” that surfaced in the last BETA version. Due to the changes in the “debug output”, it became clear that there were some issues that needed attention. The problem is related to using multiple rules on the same trigger – for example a multi choice field.
This means I’ll have to do some changes to how the “on-change rules” are handled, and release a new BETA – hopefully later this week or next weekend.
If you are happy with the functionality of the solutions and the support that I provide in these pages, I would be happy if you could write a few lines to help others to decide whether to start using them.
Write any feedback in the comments below. If you like, you can include the line of business and a bit about how it has helped to improve the SharePoint user experience in your company.
I have made some changes to how jQuery loads using the “noConflict” loading option to ensure the correct version of jQuery is loaded, and that it’s not killed by other third party code loading jQuery again in the same page.
I need some feedback on how this performs before I can move it out of BETA. Please post any findings in the forum.
If it for some reason fails to load, please open the developer console by hitting F12 > Console and post any error messages you find there.
I have also added a new functionality to DFFS that lets “Linked rules and functions” (previously “And these rules or functions are true / false”) work “on change” to trigger the parent rule when the parent rule and all linked rules are validated to “true”. This setting must be turned on for each rule by checking the “Let linked rules trigger the parent rule on change” checkbox.
This functionality should make it easier to set up more complex rules.
You find the full changelog here.
My ISP is haveing trouble with the server where I host spjsfiles.com. It will hopefully be up within a few hours, but if it’s not I’ll have to look at other methods of making the source files available.
Sorry for the inconvenience.