Controlling who students can and cannot contact via SIMPLE

[lollies]

We believe that there is a system on SIMPLE which resricts who students can communicate with and wondered what we would have to do to set this up for our own course?

Thanks,
Sarah

[mhughes2k]

The students can contact ANYONE one in SIMPLE even if they don't exist. However there is a special case in adversarial projects or any project in which there is more than one student playable Role.

In these cases there is a (rather complicated) process that must be followed to allow documents sent to a Role to be delivered to the simulation which represents that Role. If you don't perform this linking process it means that when a student sends a document to another student-played character, the document will never get delivered to its destination.

Also note, the following doesn't take place until after all of the blueprints within a project are completed and the project is deployed, so you could stop reading now....

When the project is deployed on to a Platform server and all the simulations for each Player-Character have been created (in your case) you'll have 4(?) simulations that have no connection to each other.

1. On the Manage Simulations page you can click on the "Link" item next to a simulation. This starts of a process that allows you to link another simulation (a child simulation) to a character in the current simulation.

2. So if we start off with a Pursuer simulation (sim1) we would want to firstly link it to the corresponding opposing counsel which is represented in the Pursuer simulation as the Defender Law Firm role.

3. So we would choose the simulation which represents the student's playing the Defender Character (sim2).

4. Then we tell the Platform that in sim1 we want sim2 to be linked to the Defender Character, by selecting the Defender Character.

5. Then we do similar, but tell the Platform that in sim2, we want the Pursuer Character to be linked to sim1.

<phew! />Complicated, and possible more so then neccessary (and an item to be looked at in the future), and possibly isn't entirely relevant to your original question