My Project Rostering Tools Help Desk Home Page
Click here to order a resource, log a request, ask a question...
The rationale for having conditions for having tools hosted at EMSGateway / EMSOnline
On one level, one can argue that a hosted tool should do as it pleases. But then, the actions of one tool can potentially damage another tool (a good example is the 'management of permissions', see below), and in this respect, we do ask that tools agree on certain minimum standards. In this, of course, the tools that were first on deck with EMSGateway have largely set the tone.
For more information, see text of a key email relating to this below:
Hi Michael, Chris
Tony and I spent most of today on workflows, as ________ and ________ kick into these in a serious way. These and "permissions" are the two major issues that need to be tightly controlled, as bulk users are affected on all occasions, often at the press of a single button. And the actions of every hosted tool at EMSOnline directly affects the effectiveness of workflows and permissions for every other tool - there is no possibility of them working in isolation from each other.
The updated rules are as follows, and will continue to built upon. Any emails that don't conform, let us know, and we'll update them asap.
And in particular (Tony, when u get a chance, the following is slightly different from the text you planted in ________ today):
Rgds
Damien