Knowledge Base

Auto Connection to Timer component

In the newer version of the editor, auto connections no longer exist as a connection type. The auto-advance behavior is represented explicitly using a Timer component.

1. Manual navigation (Buttons/outports): Manual connections remain as outports on the component (for example, Instruction buttons, Menu buttons, Barcode outputs. These outputs connect to the next Step.

2. Auto‑advance (Timer component): If the legacy workflow had an Auto connection (timeout), the converter adds a Timer component to represent that behaviour:

• The Timer is placed in the same Step as the component that previously had the Auto connection (most commonly the Instruction Step that is converted from a Pin).
• A Timer has exactly one out-connection to a single next Step.
• If multiple auto connections existed in the older generation from the same node, only one can be represented. The converter keeps the shortest/first and trims the rest (LOG).
• Timeout values are converted from milliseconds to seconds (rounded as needed).
• If an auto-connection with 0ms existed coming out of a Pin, the converter creates a Timer of 1s to preserve auto‑advance intent.

Note: The Quiz, Menu, and Barcode components do not support outgoing auto-connections. If the legacy workflow contains such a pattern, it is converted using best‑effort rules and flagged with a log.

Quiz 

Defines the True or False output behaviour for the question configured in the navigation pane. To test certain skills of a worker on a machine, for example, the user can place quiz components in the model that contain single-answer or multiple-choice questions. Using the right panel options of the quiz component, the user can: 

• Define the quiz component’s name (only relevant inside the editor)
• Define a question
• Define whether it is a single-answer or multiple-choice question
• Add the correct and incorrect answer(s) 
• Define if this question is offered for self-study 
• If it is offered for self-study, define how many attempts the user has to answer the question 
• Decide on the feedback the user receives when answering the question

The Quiz component name identifies it in the Spatial Editor. However, in the Spatial Workplace, only the question will be displayed. 

Single-answer and multiple-choice questions:

This setting defines how many correct answers must be selected before the question is considered answered correctly. If a single is selected, the user needs to choose only one correct answer, even if the question has more than one correct answer. If multiple is selected, the user needs to select all the correct answers for the response to be considered correct. Once the correct answer or answers have been selected, the user receives positive feedback - if defined for this question - and the step that connects to the True outport of the quiz will be activated. Likewise, for incorrect answer(s), the step connected to the false output will be activated.

Answers: Any number of possible answers can be added to a question by

1. Clicking on the Add Item button under Answers.

2. Tick the checkbox next to all the correct answers for the question.

Feedback: 

It is possible to give immediate feedback to the user about whether the question was answered correctly or incorrectly. Tick the checkboxes for positive/negative feedback and enter the respective feedback message to be shown. Positive feedback will be displayed when the correct answer(s) have been selected. Negative feedback will be displayed when the user answers incorrectly. The maximum number of attempts to answer a question incorrectly before negative feedback appears depends on the question's setting.

It is important to note that without feedback, the user will not know whether they answered the question correctly or not. 

1. Holograms are converted into a Step State within the same Step that contains the Instruction Component created from the original Pin.

2. Hologram targets become Step State targets, each placed in a separate container. Separate containers are required because each target can have its own color and related properties.

3. Hologram color is transferred to the container target color (including alpha), using the same default alpha value used for holograms.

4. Hologram style is mapped to a visibility modifier:

•  Static → Show  Pulsing → Pulse

5. Hologram animation keyframes are transferred without modification to the animation of the Step State targets.

6. Hologram transform is mapped to the Step State container transform. Animation keyframes may override this base transform.

Edge cases:

If a hologram was duplicated in the legacy editor and multiple copies existed in the same Pin with separate animations, each copy is converted into a separate model in its own container within the same Step State.

Models that were previously displayed as holograms may not appear with the same level of transparency in the New Editor.

All spatial references in a workflow are added to a single Space (e.g., Space1). Their parameters, transforms, and properties are preserved.

• Spatial reference nodes are removed from the workflow logic. The nodes before and after they are reconnected use the same connection label as before.
• If multiple Model Placement nodes existed, only the first may be kept; additional ones can be dropped and reported (LOG).
• QR code markers are removed (legacy behaviour), and the user is informed during the conversion.

After Spatial References are extracted to Spatial Tracker, the former Spatial Reference node is converted to a step with Space Preference Component, with the extracted Spatial Tracker selected as the preferred tracker. If the legacy Spatial Reference has an auto‑connection value greater than zero, a Timer component is also created on the same step.

Let's visualize these with the following transformations:

The back button behaviour:

Only incoming connections to Pins/Quiz Pins/Menus/Barcodes influence the resulting Step's Back button setting:

• If all incoming connections had Back enabled --> the Step has Back-enabled.
• If any incoming connection had Back disabled --> the Step has Back-disabled.

Back button flags on connections arriving to Scene States are ignored.

Therefore, the left configuration (legacy) is currently looking like the right configuration (new):

A Checkpoint is a step-level behaviour in the new workflows that allows a Workplace user to return to a previously visited step during a task run.

A step with Checkpoint = ON becomes a valid return point after it has been visited once. From any later step, the user can navigate back to that checkpoint and continue the workflow from there, with the workflow state restored to how it was at that moment.

Important to note that this behaviour is independent of the components inside the step.

The importance of Checkpoints:

In older generation workflows, Menu nodes are combined with two responsibilities:

1. Showing multiple outgoing connections (navigation UI).
2. Allowing users to revisit the menu after it was visited once.

In the newer version, these responsibilities are intentionally split:

• Menu component controls how the choices are displayed.
• Checkpoint controls whether a step can be revisited or not.

1.  Visiting a checkpoint

• A step only becomes a valid checkpoint after the user has visited it.
• Steps with Checkpoint = OFF can never be revisited.

2. Returning to checkpoints

• From the current step, the user can return to any previously visited step that has Checkpoint = ON.
• When returning, the workflow state is restored to the moment that checkpoint was reached.

3. Checkpoint history is linear

• If a user goes back to an earlier checkpoint, any checkpoints that were visited after that step are discarded.
• Only checkpoints in the current active path remain valid.

What Checkpoints are not meant for?

1. Checkpoints do not allow users to jump to all previously visited checkpoints across the entire task run.
2. Checkpoints do not support revisiting steps that are no longer part of the current active path.
3. The legacy behaviour, where any previously visited menu could always be revisited, is intentionally not supported in New Editor.

Legacy and the New Editor validate workflows differently.

After conversion, you may see new validation errors or warnings even if the legacy workflow is exported successfully.

Quiz conversion note: Legacy Editor allowed only True or False connection in some cases. After conversion, the new Spatial Editor requires both. The converter mirrors the existing connection’s target to create the missing out-connection and records a LOG warning.

Workflow state conversion: The legacy Editor allowed multiple visible modifiers in a Scene State Node to reference the same model target(s). Workflow State Components do not permit Scene Target Containers with duplicated model target(s).

During conversion, if a visible modifier referenced a model that already exists in the Scene Target Container(s), the existing entry is removed and replaced by the newly converted one. This guarantees that each model appears at most once in the Workflow State Component.

Some of the Legacy Editor patterns cannot be represented exactly in the New Editor. In these cases, the converter applies the best-effort mapping and emits a warning tagged as LOG.

These warnings do not block conversion but should be reviewed after migration to understand any behaviour changes or limitations.

Behavioural limitations:

• LOG: Multiple Auto connections from one node → only one timer supported (keeps shortest/first; trims others).
• LOG: Quiz with multiple True/False connections → keeps the first; trims the rest.
• LOG:Outport name/value too long (>30 chars) → trimmed to 30 chars.
• LOG: Duplicate outport names after conversion (e.g., tab‑merged pins) → renamed/trimmed to satisfy validation.
• LOG: Compression ending at workflow end → creates a Step with Workflow State + Timer 1s and flags a warning.

Unsupported legacy constructs:

• LOG: Legacy Scene State – Reset Modifier → convert to a Workflow State Component without adding Scene Model Container.
• LOG: Hologram using legacy v3d format → convert to a Step State Component without adding Scene Model Container