Error "Workflow cannot be loaded." when using Rules Action "Set a Workflow Field State"

Ok, i will keep it open then.

Indeed, the Rules Action "Set a Workflow Field State" is not needed for Workflow Field. It is there because some people might be using it.
The following fix adds some text to the Action description, telling you to use the 'Set a data value' action.

My comment #4 is not true. The default action 'Set a data value'only changes the value of the Workflow State. The action 'Set a Workflow State' also allows you to set a Comment.

( P.S. It should even be possibe to schedule a sstate change via rules.)

I am sorry for the headaches this caused you. I'm not saying that it is working - i'm saying, that it is a valid action that should work.

I did an extensive test with todays -dev version, using this rule, with a 'normal' user. The test-rule sets the node to a value that is not possible according to the Transitions settings (so, Rules overrides the configured transitions). This is the current status:
- Workflow Field: 'After updating existing content', 'Set a Workflow state...' --> OK
- Workflow Node: 'Workflow state has changed', 'Set a Workflow state...' --> OK (but you need to refresh the page)
- Workflow Field: After saving a term, set a Workflow state --> OK
- Workflow Node: After saving a term, set a Workflow state --> Not Possible --> OK

But returning to your original post:
"... but it is actually happening for all my rules triggered on an entity other than the actual workflow entity with the field."
This means you have a flag, field_collection - or other entity - with a workflow, that should change the state of a third entity?
Can you post an export of the rule?

In general, the last months, several people have mentioned they are using entityforms. I never did. Can you explain you use case?

Also, there are some issues when using third-entities: #2074859: Views displaying wrong data when using references/revisions/multiple fields

Above commit is just to make sure we both have the same state of code.
I updated comment #11.

Hi,

I am having issues with the mentioned process of transitioning into another state via rules, that is not available for the user saving an entity (node).

Since fixing WorkflowState::getTransitions() the mentioned way of changing a workflow state (workflow field in use here) through rules, that is otherwise not allowed for the current user, will not. I _guess_ this might be related to the fact, that without the mentioned fix in getTransitions, any user would receive the "Author" Role in any case.

I tracked the issue down to the way, the entity is saved via rules (field_attach_update) and the missing workflowfield_entity_insert/update calls to module_invoke_all('transition post'). Given your mentioned context:

I have a workflow field on a content type and a rule that will transition to a state via "Set a workflow state (with comment)" on "After updating existing content". The transition is not allowed for the current user and the result is the following (in this Order!)

The rule is triggered transitioning setting the state and creating a comment. OK

The entity should be saved triggering a transition from the original state to the new state failing since this is done without _force_.

I end up with a Workflow Comment in History that the state transition worked, but the entity still has the old state value in the workflow field.

Can you shed some light on why the mentioned hooks for entity_update/insert are not yet implemented? I could help, as we need this working!

Regards,

Lennart

@LCM, I could reproduce your problem. It should be fixed with adjacent commit.
In general the code struggles already for years with this scenario: "use changes state; program makes follow-up change.".
In the current version, the state change via Rules does not have to be an existing Transition. The parameter $force=TRUE makes sure some checks are skipped.

For reference, I'm testing with below Rule:

{ "rules_node_state_change_" : {
    "LABEL" : "node state change ",
    "PLUGIN" : "reaction rule",
    "REQUIRES" : [ "rules", "workflow_rules" ],
    "ON" : [ "node_update" ],
    "IF" : [
      { "entity_has_field" : { "entity" : [ "node" ], "field" : "field_workflow" } },
      { "data_is" : { "data" : [ "node:field-workflow" ], "value" : "27" } }
    ],
    "DO" : [
      { "workflowfield_field_set_state" : {
          "node" : [ "node" ],
          "field" : [ "node:field-workflow" ],
          "workflow_state" : { "value" : { "62" : "62" } },
          "workflow_comment" : "via Rules "
        }
      }
    ]
  }
}