I want to achieve loop in Resilient workflow. For example, I want to call a function repeatedly for 'n' times, the value of 'n' will vary dynamically.

When I use workflow property to store the loop count, it doesn't allow me to overwrite workflow property value to maintain the loop counter variable for iteration.

So I just want to know, is there any way to achieve loop in workflow?

Regards,
Anbalagan R

------------------------------
Anbalagan Rajagopal
------------------------------

I have not tried this, but what if you created a "middle-man" function that serves as a counter (returning simply n+1 ... results.n), and then use an exclusive gateway to either:

1.) End the loop (go to next item in workflow / end workflow) if  n = loop_max
2.) Return to original function (before "middle-man" function) if n< loop_max


The condition applied to the gateway would be (for end condition arrow):

Script condition: continue
Advanced Scripting Options:
continue = True
if(workflow.properties.workflow_middle_man_results['n'] = 100):
   continue= False

Flip True/False order for other condition.

------------------------------
Jared Fagel
Cyber Security Analyst Intern
Public Utility
------------------------------

Hello,

Just wanted to let both of you know that my team and I have tried this before and works.

Regards,

------------------------------
Carlos Ortigoza
------------------------------

Original Message:
Sent: Mon July 22, 2019 11:49 AM
From: Jared Fagel
Subject: How to achieve loop in Resilient Workflow?

I have not tried this, but what if you created a "middle-man" function that serves as a counter (returning simply n+1 ... results.n), and then use an exclusive gateway to either:

1.) End the loop (go to next item in workflow / end workflow) if  n = loop_max
2.) Return to original function (before "middle-man" function) if n< loop_max


The condition applied to the gateway would be (for end condition arrow):

Script condition: continue
Advanced Scripting Options:
continue = True
if(workflow.properties.workflow_middle_man_results['n'] = 100):
   continue= False

Flip True/False order for other condition.

------------------------------
Jared Fagel
Cyber Security Analyst Intern
Public Utility
------------------------------

Hi Carlos,

I have tried the same logic mentioned by 'Jared Fagel'. In order to make the condition check in the gateway I need to store the counter variable in workflow property, but I am unable to update the workflow property (counter variable) in the next iteration as it throws "read only" error.

Could you tel me how you have tried this with some sample code.

Regards,
Anbalagan R

------------------------------
Anbalagan Rajagopal
------------------------------

Original Message:
Sent: Tue July 23, 2019 05:15 AM
From: Carlos Ortigoza
Subject: How to achieve loop in Resilient Workflow?

Hello,

Just wanted to let both of you know that my team and I have tried this before and works.

Regards,

------------------------------
Carlos Ortigoza
------------------------------


Original Message:
Sent: Mon July 22, 2019 11:49 AM
From: Jared Fagel
Subject: How to achieve loop in Resilient Workflow?

I have not tried this, but what if you created a "middle-man" function that serves as a counter (returning simply n+1 ... results.n), and then use an exclusive gateway to either:

1.) End the loop (go to next item in workflow / end workflow) if  n = loop_max
2.) Return to original function (before "middle-man" function) if n< loop_max


The condition applied to the gateway would be (for end condition arrow):

Script condition: continue
Advanced Scripting Options:
continue = True
if(workflow.properties.workflow_middle_man_results['n'] = 100):
   continue= False

Flip True/False order for other condition.

------------------------------
Jared Fagel
Cyber Security Analyst Intern
Public Utility

Hi Anbalagan,

Sadly, workflow properties are read-only. I have used the following trick to overcome this. I create a new workflow property for the next counter value. Then, get the latest workflow property to retrieve the counter value. This technique is expensive for workspace resources and certainly not useful for large counters. But it achieves the purpose.  I've used this also to iterate through a list in a property as well.

Mark

# this technique works for counters < 100, add move zeros for larger lists
workflow.addProperty('alist', {'list': [ 'a', 'b', 'c']})
workflow.addProperty('z01', { 'counter': 0 })
workflow.addProperty('z02', { 'counter': 1 })
workflow.addProperty('z03', { 'counter': 2 })

# since 'z' is last in alphabet, will get that key sorted
maxkey = max(workflow.properties.keys())
counter = workflow.properties[maxkey]['counter']
log.debug('counter: {}'.format(counter))
incident.description = workflow.properties['alist']['list'][counter]​

------------------------------
Mark Scherfling
------------------------------

Original Message:
Sent: Tue December 31, 2019 12:55 AM
From: Anbalagan Rajagopal
Subject: How to achieve loop in Resilient Workflow?

Hi Carlos,

I have tried the same logic mentioned by 'Jared Fagel'. In order to make the condition check in the gateway I need to store the counter variable in workflow property, but I am unable to update the workflow property (counter variable) in the next iteration as it throws "read only" error.

Could you tel me how you have tried this with some sample code.

Regards,
Anbalagan R

------------------------------
Anbalagan Rajagopal
------------------------------


Original Message:
Sent: Tue July 23, 2019 05:15 AM
From: Carlos Ortigoza
Subject: How to achieve loop in Resilient Workflow?

Hello,

Just wanted to let both of you know that my team and I have tried this before and works.

Regards,

------------------------------
Carlos Ortigoza


Original Message:
Sent: Mon July 22, 2019 11:49 AM
From: Jared Fagel
Subject: How to achieve loop in Resilient Workflow?

I have not tried this, but what if you created a "middle-man" function that serves as a counter (returning simply n+1 ... results.n), and then use an exclusive gateway to either:

1.) End the loop (go to next item in workflow / end workflow) if  n = loop_max
2.) Return to original function (before "middle-man" function) if n< loop_max


The condition applied to the gateway would be (for end condition arrow):

Script condition: continue
Advanced Scripting Options:
continue = True
if(workflow.properties.workflow_middle_man_results['n'] = 100):
   continue= False

Flip True/False order for other condition.

------------------------------
Jared Fagel
Cyber Security Analyst Intern
Public Utility

I was just about to push this to the Aha since I was not aware of this limitation, but I now see this is an idea already:
https://2e4ccba981d63ef83a875dad7396c9a0.ideas.aha.io/ideas/R-I-700

I wonder if @Carlos Ortigoza used an incident field to achieve this instead (and assumed only one instance of the workflow would be run at a time per given incident)? @Mark Scherfling's workaround is interesting too!
​​

------------------------------
Jared Fagel
Cyber Security Analyst Intern
Public Utility
------------------------------

Original Message:
Sent: Thu January 02, 2020 11:00 AM
From: Mark Scherfling
Subject: How to achieve loop in Resilient Workflow?

Hi Anbalagan,

Sadly, workflow properties are read-only. I have used the following trick to overcome this. I create a new workflow property for the next counter value. Then, get the latest workflow property to retrieve the counter value. This technique is expensive for workspace resources and certainly not useful for large counters. But it achieves the purpose.  I've used this also to iterate through a list in a property as well.

Mark

# this technique works for counters < 100, add move zeros for larger listsworkflow.addProperty('alist', {'list': [ 'a', 'b', 'c']})workflow.addProperty('z01', { 'counter': 0 })workflow.addProperty('z02', { 'counter': 1 })workflow.addProperty('z03', { 'counter': 2 })# since 'z' is last in alphabet, will get that key sortedmaxkey = max(workflow.properties.keys())counter = workflow.properties[maxkey]['counter']log.debug('counter: {}'.format(counter))incident.description = workflow.properties['alist']['list'][counter]​

------------------------------
Mark Scherfling
------------------------------


Original Message:
Sent: Tue December 31, 2019 12:55 AM
From: Anbalagan Rajagopal
Subject: How to achieve loop in Resilient Workflow?

Hi Carlos,

I have tried the same logic mentioned by 'Jared Fagel'. In order to make the condition check in the gateway I need to store the counter variable in workflow property, but I am unable to update the workflow property (counter variable) in the next iteration as it throws "read only" error.

Could you tel me how you have tried this with some sample code.

Regards,
Anbalagan R

------------------------------
Anbalagan Rajagopal


Original Message:
Sent: Tue July 23, 2019 05:15 AM
From: Carlos Ortigoza
Subject: How to achieve loop in Resilient Workflow?

Hello,

Just wanted to let both of you know that my team and I have tried this before and works.

Regards,

------------------------------
Carlos Ortigoza


Original Message:
Sent: Mon July 22, 2019 11:49 AM
From: Jared Fagel
Subject: How to achieve loop in Resilient Workflow?

I have not tried this, but what if you created a "middle-man" function that serves as a counter (returning simply n+1 ... results.n), and then use an exclusive gateway to either:

1.) End the loop (go to next item in workflow / end workflow) if  n = loop_max
2.) Return to original function (before "middle-man" function) if n< loop_max


The condition applied to the gateway would be (for end condition arrow):

Script condition: continue
Advanced Scripting Options:
continue = True
if(workflow.properties.workflow_middle_man_results['n'] = 100):
   continue= False

Flip True/False order for other condition.

------------------------------
Jared Fagel
Cyber Security Analyst Intern
Public Utility

------Original Message------

Hi Anbalagan,

Sadly, workflow properties are read-only. I have used the following trick to overcome this. I create a new workflow property for the next counter value. Then, get the latest workflow property to retrieve the counter value. This technique is expensive for workspace resources and certainly not useful for large counters. But it achieves the purpose.  I've used this also to iterate through a list in a property as well.

Mark

# this technique works for counters < 100, add move zeros for larger lists
workflow.addProperty('alist', {'list': [ 'a', 'b', 'c']})
workflow.addProperty('z01', { 'counter': 0 })
workflow.addProperty('z02', { 'counter': 1 })
workflow.addProperty('z03', { 'counter': 2 })

# since 'z' is last in alphabet, will get that key sorted
maxkey = max(workflow.properties.keys())
counter = workflow.properties[maxkey]['counter']
log.debug('counter: {}'.format(counter))
incident.description = workflow.properties['alist']['list'][counter]​

------------------------------
Mark Scherfling
------------------------------

Memory is freed when then workflow is complete. We do have outstanding enhancements to support updates to workflow properties. Not that enhancement is currently not scheduled.

Regards,
Mark

------------------------------
Mark Scherfling
------------------------------

Original Message:
Sent: Thu January 02, 2020 12:12 PM
From: Anbalagan Rajagopal
Subject: How to achieve loop in Resilient Workflow?

Hi Mark,

Thanks for your prompt reply, exactly the same technique I am using currently. Everytime I create a new workflow property for counter variable and comparing them with main list property. And it's working fine.

And I hope all the workflow memory (allocated for propertied) will be released as soon as the workflow ends the execution.

It would be very helpful if you provide an option to modify the properties.

Thanks & Regards,

Anbalagan R

Get Outlook for iOS

On Thu, Jan 2, 2020 at 9:33 PM +0530, "Mark Scherfling via IBM Community"

Original Message------

Hi Anbalagan,

Sadly, workflow properties are read-only. I have used the following trick to overcome this. I create a new workflow property for the next counter value. Then, get the latest workflow property to retrieve the counter value. This technique is expensive for workspace resources and certainly not useful for large counters. But it achieves the purpose.  I've used this also to iterate through a list in a property as well.

Mark

# this technique works for counters < 100, add move zeros for larger listsworkflow.addProperty('alist', {'list': [ 'a', 'b', 'c']})workflow.addProperty('z01', { 'counter': 0 })workflow.addProperty('z02', { 'counter': 1 })workflow.addProperty('z03', { 'counter': 2 })# since 'z' is last in alphabet, will get that key sortedmaxkey = max(workflow.properties.keys())counter = workflow.properties[maxkey]['counter']log.debug('counter: {}'.format(counter))incident.description = workflow.properties['alist']['list'][counter]​

------------------------------
Mark Scherfling
------------------------------

Hi Rajagopal,

Were you able to achieve the same, we have a similar requirement f looping a function "n" times.

We take the output from a function which is an array, we would want to loop through the array and pass each value to a different function in a loop.


Please kindly suggest the best way possible.

------------------------------
Rambatla Venkat Rao
------------------------------

------------------------------
Mike Beaver
------------------------------