Editing a Resource

To edit a Resource:

1   From the Resources list, right-click and select Edit, or double-click a specific resource record to directly edit that record.

The selected Resource page appears.

For a full view of what is on the page, see Creating a New Resource.

2   Modify or add additional data in the appropriate fields.

3   Click Save to remain on this page or click Save and Close to save the Resource and return to the Resources list.

 

Editing Multiple Resources

To edit multiple resources:

1   Select the desired resources, right-click and select Edit Selected Resources.

The Edit Multiple Resources page appears. It is blank so that you can enter the new values for the selected resources.

2   Make edits as needed in the appropriate fields.

3   Click Save to save the new information for the selected resources. The new information is applied to the selected resources.

Capping Generated Window Open and Close Values

The Earliest Hr Gen OpenWindow and Latest Hr Gen CloseWindow fields allow users to put a cap on how early a generated time window can open and how late a generated time window can close. If the generated time windows resulting from any of the following operations exceed the cap values set in the Earliest Hr Gen OpenWindow and Latest Hr Gen CloseWindow fields, the cap value is used instead.

Lock Generated Time Windows operation

• Route moved to another schedule

• All routes moved to another schedule

• Status updated from first status call

For example, if a user selects the Lock Generated Time Window option for a route in the Routes quadrant and the generated open time window is earlier than the cap value entered in the Earliest Hr Gen OpenWindow field, the cap value is used instead.

Please note the following the following exceptions regarding this feature:

• If the Projected Arrive Time is earlier than the Earliest Hr Gen OpenWindow value, the Projected Arrival Time is used instead.

• If the Projected Departure Time is later than the Latest Hr Gen CloseWindow value, the Projected Departure Time is used instead.

Note - In these cases, users should fix the route starting and ending times since the resource settings conflict with the cap values provided.

• If no value is entered in these fields, no cap is enforced.