Hi. In my app we track the validity of a user's session with an event handler & microflow that runs whenever an entity is modified. The app also has some scheduled tasks that we don't want that microflow to run for (since there will be no user session). To achieve this at the start of the microflow I used a java action to retrieve the executionType from the current context. My assumption was that the scheduled tasks would have an executionType of SCHEDULED_EVENT, but they are coming through as CUSTOM instead. Does anyone have any explanation of the different executionType enums? I can obviously skip the session check where executionType is CUSTOM, and it'll work - but without fully understanding what else CUSTOM may entail, I don't want to just go ahead and add that and potentially create a security hole.
asked
Simon Wallis
1 answers
0
now thinking context().getSession().isSystemSession() may provide what I need instead..