Referencing a Task in another Workspace

[s.r.hoover]

Using an Action Script, We are trying to send an email to a specific user when a task is completed that informs them that another task from another workspace needs to be completed.  Is there a way to reference this task that is in the other workspace in the workspace that we would currently be working in?

[jpiggee]

Scott,

Yes this is doable by a couple of methods, the two easiest ones would be to have the task as part of the Project management tab on the primary site from which you’re looking from. The second option would require a link to the task workspace item in question where you could then check to see what state the item is in. You could also use the Relationship array and the Linked/Managed Items array.

What it boils down to is: If you can click on something to see the task, than you can reference it.

Or if you want a real challenge you can do with without being able to click on it, but it would require the knowledge of where it’s located and how to properly update this location in your script without having a clear idea of what the dmsID of task is that you’re looking for.

[s.r.hoover]

Joe,

We have figured out the first two methods as you described already.  Would you be able to explain the third method, how to reference a task without clicking on it.  

Thanks,

Scott

[jpiggee]

So in order to do a non-click method, somehow the master workspace would need to know the dmsID of the sub (task) workspace and store it somewhere, or the sub workspace would need to know the master workspace and send its dmsID to the master for storage on reference latter.

This can be completed in a couple different ways, by creation/manipulation of the sub by master, creation/manipulation of the sub with knowledge of the master by itself or the creation/manipulation of another workspace that knows who the master and sub is.

*So in short, if the nothing in the system has the master or sub tied together, there is no way to transfer the information, unless one of the items is a static dmsID (meaning a single item in a workspace that will be added too every time).

As I stated this is a very difficult route to go and even more difficult depending on how the workspaces are setup and/or interact.