Once they have been configured, which actions are allowed to be repositioned to another location...

Comprehensive and Detailed Explanation:

In OIC’s orchestration-style flows, certain actions can be moved on the canvas post-configuration:

Stage File Action - Write File (B):This operation (writing to a staged file) is movable as it’s a standalone action.

JavaScript Call Action (D):Invoking custom JavaScript is flexible and repositionable.

Stage File Action - Read File (F):Reading an entire file is a movable, independent operation.

However:

Stage File Action - Read File in Segments (A):This operation involves iterative processing (e.g., scopes for segments), restricting its mobility due to dependencies.

Switch Action (C):As a conditional branching structure, it’s less flexible once branches are defined.

For Each Loop Action (E):Its iterative nature ties it to specific data structures, limiting repositioning.

This reflects OIC’s design constraints for complex, dependent actions.