The Create bookentry from shipment tab contains one selection field each for the specific dynamic enumerations that the Time slot management module provides for the classification of time slot bookings.

Each parameter corresponds to a field in the 'Time slot booking' data model, for which a static assignment can optionally be defined:

Package types

packageType

Type of vehicle

typeOfVehicle

Kinds of goods

kindOfGoods

Mode of transport

modeOfTransport

In the second tab Copy attributes, a Repeatable element optionally allows the configuration of multiple value resolvers for attributes whose value is copied from the shipment to the new time slot booking.

►IMPORTANT◄ Unsuitable configurations for Copy attributes lead to an error with a rollback at runtime. The following rules must be observed:

1. The attribute type must be applicable for the 'Time slot booking' entity type (see Input forms for time slot booking for applicable attribute types).
   
   

2. Plural attributes cannot be copied even if they are applicable to a 'Time slot booking' according to their type. The 'Example' (below) shows how they can be transferred.
   
   

3. The value resolver for All attributes of one type cannot be used to copy attributes of a type across the board.

Via the symbols and configurations for Copy attributes can be added or removed. Within each instance created, a value resolver must be used that returns a complete, single attribute of the shipment that is applicable by type to the time slot booking. Typically, a Typed attribute resolver is used for this purpose.

Shown on the right is a data input form for shipments of the 'Toxic waste disposal' Shipment type with the following characteristics:

• Since a 'toxic waste' shipment in our case should always be 'bulk', only two numerical attributes Gross volume and Gross weight are provided. For planning the unloading, only the 'Gross volume' in the binding preset Volume unit 'Cubic meter' is decisive.

• The time attribute Arrival date planned provides information about the scheduled time of delivery.

• The company attribute Carrier specifies the company responsible for the transport.

• The following 'Reference attributes' qualifes various characteristics of the shipment, each of which can occur either once or multiple times.

• A list of container identifiers in the plural text attribute Container No follows below, which makes it possible to trace the origin of the shipped waste if required.

As far as this information is relevant for unloading, it should also be visible in a 'Time slot booking'. From the controller's point of view, this data should appear in the Booking overview as shown below:

An event handler for the Triggering event 'Create header from shipment' (see Time slot management tool (Events) is created and configured as follows:

• The Validating rule here combines a type check for the 'Shipment' entity type with an object field rule that checks whether the shipment type 'Toxic waste disposal' is specified. Details on this are omitted.
  
  ►NOTE◄ The Triggering event provides the same shipment as the only element of a list in the shipments variable. Only this is immediately processed by the event action Create bookentry from shipment.

The Action on passed rule is first shown here in overview and will be highlighted in more detail in the following sections:

• In the first step, the event action Create bookentry from shipment is executed to create a time slot booking for the shipment and initialize it using the means of the event action.

• The following Execute with event action accesses the created time slot booking via the header variable, which should be present in it as the only element of a list after the Buchungseintrag aus Sendung erzeuge event action has been executed. In addition to adjustments to the time slot booking that are not directly possible via the dafault functions, a reference to the newly created time slot booking is also set up in the shipment data in the process.

• Finally, the event action Save changes later for must be executed with the shipment as the reference object so that the created reference is saved.

The event action Create bookentry from shipment is configured as shown on the right:

• In the Create bookentry from shipment tab, some of the optional parameters are used to define static assignments for fields of the new time slot booking. The following classification should apply to all shipments for which the Validating rule (see above) applies:
  

  • The delivery is always made by the Type of vehicle 'Barge'.

  • The type of goods is always 'Bulk'.

  • The Mode of transport is always 'Sea freight'.

►NOTE◄ The Type of packaging is not set statically here. In the post-processing of the time slot booking, an assignment for the field could be made starting from data of the shipment. However, this is not necessary.

In the second tab, Copy attributes, the Typed attribute resolver is used four times to specify attributes of the program as copy attributes:

• Date attribute for the Date types 'Arrival date planned'.

• Company attribute for the Company type 'Carrier'.

• Numeric attribute for the Numeric types 'Gross volume'.

• Numeric attribute for the Numeric types 'Gross weight'.

At runtime, this configuration causes corresponding typed attributes to be created in the data of the new time slot booking, provided that the shipment contains corresponding data.

►NOTE◄ Whether the Booking overview contains elements for the display of corresponding details (see Input forms for time slot booking) is irrelevant for the creation of the attributes. However, it is crucial that only attribute types are used that are supported in principle for the 'time slot booking' entity. In the present example, against this background, on the one hand the 'Reference attributes' of the shipment are problematic, since this attribute type is basically not applicable in time slot bookings. On the other hand, the plural text attribute 'Container No' cannot be copied with the standard methodology.

Copy attributes tab:

Since not all data from the shipment can always be transferred to the newly created time slot booking using the default methodology, here are some options for specific 'post-treatment' of the entity:

• Within the Execute with event action shown on the right, the time slot booking is first defined as a different reference object for the subsequent event actions. The event action Create bookentry from shipment returns the time slot booking via the header variable as the only element of a list that was previously initialized when the event was executed (empty). The List item value resolver concatenated with the Variable value resolver with the Offset value of 0 defines first (here: only) element of the list.

• The following Set value event action assigns a string to the Remarks (remarks) field that is generated from a list of all reference attributes (see All attributes of one type) via Collect values as a Concat strings of Reference type and the value of the 'reference' (reference) per attribute. The output can be seen in the runtime example above. Details are omitted.
  ►NOTE◄ The 'references' are only reproduced informatively by the concatenation. Systematic access to individual values is then only guaranteed to a limited extent. For the controller responsible for planning, the mirroring of the shipment data in this form should be sufficient.

• The following Set value event action transfers the 'Container No' list from the plural text attribute of the shipment directly to the corresponding attribute of the time slot booking. Here, for source and destination, the Plural typed attribute resolver can be used successfully – unlike the Copy attributes tab of the Create bookentry from shipment event action.

• With Save changes later, the new time slot booking is then marked for saving at the end of the transaction. This will immediately assign an ID to it. Which is needed for the next step.

• Per Set value, the ID of the new time slot booking is noted as 'linkedEntityId' in a linked entity attribute (with the 'Time slot booking' type – SHIPMENT_TO_BOOKING) provided for this purpose in the shipment.