Terminate workflow from policy?

[jvybihal]

Hi, I am today before a situation, where I would like to treminate/retract running workflow from my policy.

My situation:
On DTX publisher channel, I have -ctp- policy testing if attributeX is changing. When it is changing, start workflow, and strip the attributeX from operation. The PRD is single YES/NO approval. If approved, the attributeX is changed on destination object. If denied, no change is made.

This works great, but there is one issue with this I recently found out:
When attributeX changes to "A", WF is started, and approval is pending. And when approval is pending, and attributeX changes to "B", there are two approvals pending, and so on. If they are processed by approver in wrong order, the object ends up with obsolete value. What I would like to do, is, that when attributeX changes to "A", WF is started and approval is pending, but if attributeX changes to "B", while approval is pending, the previous workflow(s) should be terminated and only one (the most recent) approval should be pending.

Now, I am not sure, what approach should I take, or if there is any, or I am doing things in a wrong way. I came across geoffc's "Using SOAP to terminate a running workflow" cool solutions, but I am not sure, if that would be the right approach, also the article feels little bit old. Also I read here on forums, from Steven Williams, that retraction is not yet possible, but that was from 2014, so I am really not sure how things moved since then.

[lhaeger]

jvybihal wrote:

> I read here on forums, from Steven Williams, that retraction is not yet
> possible, but that was from 2014, so I am really not sure how things
> moved since then.

Did you check
https://www.netiq.com/documentation/identity-manager-developer/rest-api-document
ation.html for an API supporting your needs?

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)

[jvybihal]

lhaeger;2483977 wrote:
jvybihal wrote:
Did you check

I did yesterday, but briefly, nothing that did stand out for me. But I will recheck more thoroughly today.

[geoffc]

On 7/13/2018 3:36 AM, jvybihal wrote:
>
> lhaeger;2483977 Wrote:
>> jvybihal wrote:
>> Did you check
>>
>
> I did yesterday, but briefly, nothing that did stand out for me. But I
> will recheck more thoroughly today.

How about these articles of using a workflow with an integration
activity calling the SOAP terminate workflow in it?


https://www.netiq.com/communities/cool-solutions/using-soap-terminate-running-workflow-part-1/
https://www.netiq.com/communities/cool-solutions/using-soap-terminate-running-workflow-part-2/

[lhaeger]

Geoffrey Carman wrote:

> How about these articles of using a workflow with an integration activity
> calling the SOAP terminate workflow in it?
>
>
https://www.netiq.com/communities/cool-solutions/using-soap-terminate-running-workflow-part-1/
>
https://www.netiq.com/communities/cool-solutions/using-soap-terminate-running-workflow-part-2/

Seven years since you published this and there's still no direct way to
terminate a running workflow?

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)

[cpedersen]

On 13.07.18 15:16, Lothar Haeger wrote:
> Geoffrey Carman wrote:
>
>> How about these articles of using a workflow with an integration activity
>> calling the SOAP terminate workflow in it?
>>
>>
> https://www.netiq.com/communities/cool-solutions/using-soap-terminate-running-workflow-part-1/
>>
> https://www.netiq.com/communities/cool-solutions/using-soap-terminate-running-workflow-part-2/
>
> Seven years since you published this and there's still no direct way to
> terminate a running workflow?
>

File an enhancement request.


Casper

[geoffc]

On 7/13/2018 9:16 AM, Lothar Haeger wrote:
> Geoffrey Carman wrote:
>
>> How about these articles of using a workflow with an integration activity
>> calling the SOAP terminate workflow in it?
>>
>>
> https://www.netiq.com/communities/cool-solutions/using-soap-terminate-running-workflow-part-1/
>>
> https://www.netiq.com/communities/cool-solutions/using-soap-terminate-running-workflow-part-2/
>
> Seven years since you published this and there's still no direct way to
> terminate a running workflow?

No comment.

I am on a bug that they want to close because it is already documented,
(Password Troubleshooter Tool) and the docs basically say, use the tool,
it helps diagnose stuff. And here is a single reg key of interest...

I suggested that maybe the 3 year old articles I wrote on the topic
could be linked in, instead, just to make life simpler on them....

[Alex McHugh]

Geoffrey Carman <geoffreycarmanNOSPAM@NOSPAMgmail.com> wrote:
>
>
> I am on a bug that they want to close because it is already documented,
> (Password Troubleshooter Tool) and the docs basically say, use the tool,
> it helps diagnose stuff. And here is a single reg key of interest...
>
> I suggested that maybe the 3 year old articles I wrote on the topic
> could be linked in, instead, just to make life simpler on them....
>
>

Don’t forget everything that is officially documented incurs a maintenance
and support overhead. The current balance is unfortunately too far towards
minimising such overheads to the absolute bare essentials. MF can’t
realistically be expected to document as detailed as you often manage.

[geoffc]

On 7/15/2018 5:08 AM, Alex McHugh wrote:
> Geoffrey Carman <geoffreycarmanNOSPAM@NOSPAMgmail.com> wrote:
>>
>>
>> I am on a bug that they want to close because it is already documented,
>> (Password Troubleshooter Tool) and the docs basically say, use the tool,
>> it helps diagnose stuff. And here is a single reg key of interest...
>>
>> I suggested that maybe the 3 year old articles I wrote on the topic
>> could be linked in, instead, just to make life simpler on them....
>>
>>
>
> Don’t forget everything that is officially documented incurs a maintenance
> and support overhead. The current balance is unfortunately too far towards
> minimising such overheads to the absolute bare essentials. MF can’t
> realistically be expected to document as detailed as you often manage.

I accept and understand that. I would appreciate some linkages to help
people out thouogh.

[rrawson]

I am about to publish a cool solution on how to make SOAP calls into UA directly from policy. I wrote a simple java class to bolt into the engine to do this. The example is to approve a workflow task (to send back data set by the engine into the workflow so it can make a rest call and so it appears in the comment history). But it could also be morphed easily into any sequence of SOAP calls to the UA or to any endpoint for that matter. Stay tuned....