Extension or Available pega activity on flow action Post Processing ?
What would be the Extension or Available pega activity on flow action which application can extend on Post Processing ? "Work-.PerformDefaults" is not serving the purpose. In Flow Action post processing "FinishAssignment" activity is being called and "Work-.Perform" is conditional in the activity. "Work-.Perform" calls the "Work-.PerformDefaults"
Pega version - 7.1.9
Message was edited by: Marissa Rogers - added category
Is PerformDefaults supposed to run as a pre-processor for each assignment or as a pre-processor for each flow action or as a post-processor for each assignment or as a post-processor for each flow action ? /Eric
I guess what I'm trying to clarify is, are you finding that the behavior of PerformDefaults is in agreement with the documentation and your needs are different? Or are you finding that the behavior is disagreeing with the documentation? Or are you finding that the documentation doesn't sufficiently say?
My understanding is that PerformDefaults is useful for situations in which you want common behavior for all flow actions rather than just for one. However, I do not remember whether that common behavior occurs at flow action pre-processing time (or beforehand, so that it precedes specific flow action pre-processing rule?) or whether it occurs at flow action post-processing time, or whether it occurs at the beginning or end of the assignment so that multiple local flow actions (those that don't advance the assignment) could be performed without repeating the PerformDefaults for each one. Hopefully the documentation clarifies all of this!
If you find the documentation lacking in this area, please let us know here at Pega so we can improve it. Also, to get some of the actual answers without waiting for the documentation to be clarified, I suggest you trace your flow and look through the trace to see where PerformDefaults is actually called. /Eric
Called by the Work-.Perform activity. Override to customize or extend the steps that are performed while processing an assignment.
2. Documentation present in History tab of the PerformDefaults activity is below:
Called from Work-.Perform, this extension point activity allows the user to customize or extend the steps that are performed while processing an assignment.
The documentation of both does not clarify whether it is done on Post or Pre of Assignment/FlowAction
I feel this discussion is more going towards PeformDefaults rather I want to know what would be the Extension activity I can use on Submit of flow action ? If PerformDefaults is not the answer, please suggest the alternative
Usually, extension points exist even if you don't create one. So, for example, even if you don't create any PerformDefaults, you'll still see it in the tracer, since the stub activity version of PerformDefaults runs.
So, you can run the tracer and look for stub extension points. /Eric
I have done my analysis in advance before creating the question in this forum. I have ran tracer, searched PDN, searched Mesh as well in advance before posting this. I was not able to find any activity(whose status is available or extension) where I can plugin generic logic on submitting of flow action.
now, can you help me know if there is anything can be done on post of flow action ?
Sorry I'm jumping on the conversation but why are you not using the post activity on FlowAction as suggested previously by Phani Sahukaru ? If you cannot find any extension point I guess this is your best option, make sure you are calling your common activity on all FlowAction in your application.
If I understand correctly, you want something that will run AFTER you hit submit. PerformDefaults fires on your way into the perform harness, so isn't the right choice. I did a quick search and didn't find any extension point that seemed to fit the bill. If it's too much of a bother to update the post processing activity of every flow action (and that's a bit understandable), could you create your activity and put it into a utility shape that you place into flows? That is likely still a log of Do you need to fire the activity when you local actions or just for progressing in the flow? You might be able to get away with something like a Rule-Declare-Trigger, depending on what your business needs are. It might help if you went into more detail about what you are trying to do in the activity since there might be a better way to do it.
Thanks Mike , you understood my concern and even cleared the doubt of PerformDefaults which is like being called on pre processing of assignment.
let me tell you my need based on which you can suggest what best suits:
we have some Business information on every flow action which needs to be sent to a third party system so we are calling a third party system(via connectors) on SUBMIT(not on SAVE) of every flow action .
this is for the reason I was looking for something generic where I can plug-in this connector