During enrichment, blueprintsprocessor creates a dynamic datatype for each workflow that includes the resource resolution component with mapping-file artifacts. The current logic only considers the target node template of the first step. In imperative workflows where RR component is used as subsequent step, the dynamic data type is not created, which prevents resolving workflow input properties.