Scheduling a time segment

Levels

Levels define a priority between different time segments, and a higher-level time segment takes precedence over lower-level time segments, except for the Application-Bus-Time2-Get-Free-Window scenarios commands. For more information, see Application-Bus-Time2-Get-Free-Window-scenarios. Levels can be from 1 to 1000. 

Levels 1 and 2 have the following meanings.:

• Level 1 time segments are "available" and can be used to define workdays. 
• Level 2 time segments are "unavailable" and can be used to define holidays. Because higher-levels of available segments can override Level 2 time segments, if you do not want to override holidays, define holidays at a level higher than all other levels.
• Other time segments at Level 3 and above can either be "available" or "unavailable."

For same-level time segments, the order of overlapping activities is not guaranteed. The business component in AR System determines the final list for these time segments in the order they are retrieved.

Levels are used to determine the order in which overlapping or non-overlapping time segments take effect. In Workday and activities for one day example in Business-Time-introduction, Time Segment 2 is at a higher level than Time Segment 1. Hence, in the final list, the time window from 1:00 P.M. to 2:00 P.M. is defined as unavailable.

Time segment entity associations

The Business Segment-Entity Association form stores associations between the Business Time Segment form and the Business Time Shared Entity form. 

Business Segment-Entity Association form

The Business Segment-Entity Associations form contains the following primary fields:

• Entry ID—An identifier for an entity to which the time segment is being applied, such as an asset or a change request.
• Entry Owner ID—An identifier for the parent object owner of the entity. Allows you to identify the original owner to determine whether you can change the association.
• Time Segment ID—A time segment name that was defined on the Business Time Segment form.
• Assignee Groups—Groups specified on Business Time Segment form.

Time segment shared entities

The Business Time Shared Entity form stores logical references to a scheduled time segment. An entity can define any generic object, for example, a business event or an asset.

Only one entity of the same type can exist in this form. After an entity is created, you must reuse the existing copy in the entity from this form.

Business Time Shared Entity form 

The Business Segment-Entity Association form contains the following primary fields:

• Entity Type—Determines how the values are mapped to the Attributes fields. It is used to classify the type of entity being created. Depending on this value, it determines how the values are mapped to the Attributes fields. For example, if you have Entity Type defined as "Category," then you can map Attribute 1 to store Category 1 field data, Attribute 2 to store Category 2 field data, Attribute 3 to store Category 3 field data, and so on.
• POID—Contains the Parent Object Instance ID field. It is used to reference any desired generic object. Typically, it references the Instance ID of the parent object.
• Attribute fields—Includes a set of 10 generic attributes that can be used to describe an entity. Any character values can be mapped into these fields to describe an entity.