SetState plugin is not triggered when status is changed from custom workflow activity

(0) Share

Report

Posted on by Community Member

Hello guys,
I have a custom workflow activity . This custom workflow activity as part of its functionality changes the status of a quote record.
Now this custom workflow activity is not executed from the quote record. It is executed in the background
on a different entity. There is also a few plugins which has steps on SetState of quote entity.Specifically 5 steps. (4 on pre-operation and 1 on post operation.)
Now I am under the assumption that, when the custom workflow activity changes the status of the quote record, these 5 steps of plugin needs to be executed. Isn't that expected behaviour? Because right now it is not happening in my case. None of the plugins are executed.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Alex Fun Wei Jie 33,628 on at

Like (0)

Report

Hi,

Please check following items:

1. you should be using EntityMoniker instead of Target.

2. you need to register the plugin to both SetState & SetStateDynamicEntity messages.

Refer to below article for reference purpose.

thomasthankachan.wordpress.com/.../plugin-usage-of-setstate-and-statestatedynamicentity-message

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello Wei,

Thank you for the response. If you are referring to using EntityMoniker to change the status of the quote - Yes, I am using EntityMoniker. The plugin is also registered in both SetState and SetStateDynamicEntity. Both are preoperation, synchronous, and execution order is 5. The custom workflow which updates the status of the quote updates it from a different entity. Hence, I am not on the quote record when the status is being changed. Does this matter?

Was this reply helpful? Yes No
Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

It doesn't matter where you are changing the plugin from, SDK, Workflow, Api... The Plugin Step Message should still execute.

I would add some tracing into the Plugin and see if it executes at all and exits at a particular location, or does not execute at all.

EDIT: Even better, since you are running On-Premise, use Remote debugger and check where the issue is by adding a breakpoint to your code in the Plugin code.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello Aric,

Thank you for the response. I can confirm that the plugin is not running because I setup a test message in one of the fields and it did not get populated.

Was this reply helpful? Yes No
Suggested answer

Elliott 125 on at

Like (0)

Report

It could be that you have plugins registered on the SetState message of quote, but instead the custom workflow activity is changing the statecode/statuscode attributes?

If this is the case you could either update the custom workflow activity to use the SetState request, or register the plugins on Update instead, filtering to only the statecode/statuscode attributes.

Was this reply helpful? Yes No