If it will always be the same project, in the $Parent field you would select "object" from the coding helper and then browse to the specific project you are referring to. If the project will be dynamic, then it may be a bit more tricky. I would hop on a Q&A to go over options for the dynamic project selection because it really depends on where the rule is being created and the use case.
Post
FollowSyntax for workflow rule (NewObject, shortcut)
Hi,
Could anyone help me to figure out the syntax for a new workflow rule?
When a new task is added (under certain conditions) I want the workflow rule to create a shortcut of that task in another project.
Under "Set Actions" I have "NewObject = new Shortcut", but then I can't figure out what needs to be set for $Parent and $Child
Cheers,
Rob
Please sign in to leave a comment.
4 comments
Date
Votes
So, you cannot create a shortcut in another project?
That is rather unfortunate ...
Mmmm.
Hi Rob,
Of course you can create a shortcut of that task to another project. That's one of the basic capabilities of shortcuts and this can be done through workflow rule as well.
All you need to do is make sure you set parent = other project object, Child = CurrentObject()
Let me know if it works for you.
Rachel
Hi Rachel,
I figured as much. Thank you, that worked!
Cheers,
Rob