Browsing Spanish translation

69.

Work Breakdown Structure Code

141.

Controls resource overbooking when scheduling

151.

<para>The scheduler used for calculating the project schedule.</para><para>The default built-in scheduler is the Network Scheduler.</para><para>Other schedulers presently available is RCPS if libRCPS is installed on your system. RCPS is a genetics based resource constrained project scheduler.</para>

161.

The relations time lag

423.

The Work Breakdown Structure introduces numbering for all tasks in the project, according to the task structure.
The WBS code is auto-generated.
You can define the WBS code pattern using the Define WBS Pattern command in the Tools menu.

538.

<title>Resource Editor</title><para>Resources are organized in a Resource Breakdown Structure. Resources can be of type <emphasis>Work</emphasis> or <emphasis>Material</emphasis>. When assigned to a task, a resource of type <emphasis>Work</emphasis> can affect the duration of the task, while a resource of type <emphasis>Material</emphasis> does not. A resource must refer to a <emphasis>Calendar</emphasis> that defines the working hours.</para>

539.

Add Resource Group...

546.

Delete Selected Accounts

565.

<title>Work & Vacation Editor</title><para>A calendar defines availability for resources or tasks of type <emphasis>Duration</emphasis>. A calendar can be specific to a resource or task, or shared by multiple resources or tasks. A day can be of type <emphasis>Undefined</emphasis>, <emphasis>Non-working day</emphasis> or <emphasis>Working day</emphasis>. A working day has one or more work intervals defined. A calendar can have sub calendars. If a day is undefined in a calendar, the parent calendar is checked. An <emphasis>Undefined</emphasis> day defaults to <emphasis>Non-working</emphasis> if used by a resource, or <emphasis>available all day</emphasis> if used by a task. </para>

568.

Delete Selected Calendar