OmniPlan projects contain tasks that are accomplished through the use of resources that are both humans and machinery. The relationship between tasks and resources are defined through assignments between a resource and a task.
The value of the properties of an Assignment instance determine the nature of the assignment relationship.
Here are the properties of an instance of the Assignment class:
isLocal (Boolean r/o) • Whether this assignment is part of this project or not. A non-local assignment comes from sharing resource loads from a server project repository.
resource (Resource r/o) • The Resource of this assignment.
specificAssignments (Array of Assignment r/o) • When the assigned resource is to a resource group, the specific resources within that group who are actually assigned to do the work.
task (Task r/o) • The Task of this assignment.
totalCost (Number r/o) • Total cost of this assignment.
totalDuration (Number r/o) • Total duration of this assignment.
totalEffort (Number r/o) • Total effort performed during this assignment.
unitsAssigned (Number) • Resource units assigned to this task.
The functions that can be run on an instance of the Assignment class:
remove() • Call to delete this assignment, removing it from it’s task and resource.
Creating an Assignment
To create an instance of the Assignment class use the addAssignment(…) function of the Task class.
addAssignment(to:Resource) → (Assignment) • Create a new assignment to the given resource.
To create an object reference for a specific resource, use the resource(…) method of the Scenario class, as demonstrated in the following script example:
|New Assigned Task|
|01||rsc = actual.resource("Margret Jensen")|
|03||task = actual.rootTask.addSubtask()|
This webpage is in the process of being developed. Any content may change and may not be accurate or complete at this time.