Process flow monitor for system flows without developer mode

Hi ​@Geurt,

To get this working in such an environment, you need Developer mode rights, which can be granted in IAM:

Authorization > Users > Administrators > Developer mode

Does this help?

Hi ​@Jeroen van den Belt,

I have turned on the Developer mode rights:

But the process flow monitor remains the same. Does the change require an additional action?

Kind regards,

Mark

Hi Mark,

The Process flow monitor only can start system flows for SF runtime configurations. If you open this screen via Indicium and there is no Software Factory (with sf alias), then the bar to select a flow is hidden. Could that be the case?

If you do have a Software Factory application in the IAM the Indicium is targetting, and you have System flows which are no subflows and still do have have this option, then I think we have to dive in via a ticket.

Hi Mark.

There is no SF application in the IAM on the test and acc IAM. There is one on the dev IAM, which explains why it works on dev but not on test or acc. 

So the only way to get this working is to deploy an SF database and create an application for it in the test and acc IAM's?

If you would indeed place the SF applicatoin in there and target that to the development SF, or another SF instance with the same model as in Development, you could make that work yes. The invocation of System flows is meant to be a development feature to test your flows.

You could also opt to do a POST request to Indicium to invocate the System flow that way. Docs on that here: Process flows API | Thinkwise Documentation

​@Geurt ​@Mark Leunissen I’ve had conversations about this internally and can imagine why you would want a similar option on other environments too. But before I make assumptions, could you clarify why you would want to have such an option?
 

Note that, instead of the option to start if from the Process Flow monitor, we also considered the ability to be able to start it from IAM > System Flows screen as a ‘one-time schedule’.

​@Arie V 

The reason we want to have the option to test system flows is that the set up of the dev/test and acc differ. Dev/test are set up on Azure, where ACC is set up on premise. This results in system flows working differently on both environments. 

For example: We have a system flow that inserts documents into a folder. This doesn't work on dev/test, so it can't be tested properly on dev/test. The flow does work on ACC, but testing the system flow is a lot harder without the process flow monitor. Which often results in setting a dummy task up in the flow, which results in more deployment work.

I do understand that the difference in set up per environment is unwanted, however, that is something that can't be changed in the foreseeable future.