Extranet 5.6 includes an early peek at what I expect will become an important tool for those of you who have implemented multiple solutions in your site. It’s called “Module and Solution Support” and its goal is to allow for the independent development and release of configuration updates between the different solutions you are maintaining.
Before you get too excited, it’s important to realize that as promising as this feature is, it’s not a panacea. There are many methodologies and project management techniques to deal with your constantly evolving workflow solutions and, while this enhancement adds another tool to your toolbox, it doesn’t meet every need you could imagine. What it does provide, however, is a big step toward being able to manage different solutions on different development schedules.
Enabling this option is a one way trip so it’s best to first explore this new feature in an isolated experimental development environment. If you…
- are already familiar with using Process Studio to manage the development of your site,
- have more than one solution deployed (such as IRB, IACUC, COI, etc.), and
- face the challenge of wanting to deploy updates to the different solutions on different schedules,
then Module and Solution Support is worth a look. I’m currently using this feature on one of my projects and will update you all on my experience in a later post.
Module and Solution Support is provided as a technology preview with Extranet 5.6 and is only one of many cool new features. Start planning for your upgrade today using the Extranet 5.6 Pre-Installation Package. If you want to know more about how to upgrade, drop me an email, and I’ll fill you in on the details. To accelerate your upgrade, check out our new Extranet 5.6 Upgrade Service.
Cheers!
No comments:
Post a Comment