You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hi - We have configured the iflow "Analytical Reporting - Template Name - Async Fetch and Reporting" for template as per the config guide.
When we deploy it, iflow is always going through route highlighted in attached ScreenShot-1. This is due to properties "AdhocJob" & "ScheduledJob" created in "Initialization" step always returning as blank. These properties created in "Initialization" step as Global Variables.
Question:
How and which process/iflow creates these global variables ?
Do we have to run any other iflow that creates these global variables ?
Please correct me if my understands of this iflow is wrong.
Regards,
Kishore
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
Screenshots
Attached ScreenShot-1
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
thank you very much for your request:
Please find below response
How and which process/iflow creates these global variables ?
iFlow – ‘Analytical Reporting - Template Name - Async Fetch and Reporting’ creates the local variables (not global). These also get cleared off post-report generation refer to SubFlow - Post Execution Clearance
iFlows should be copied per template.
Do we have to run any other iflow that creates these global variables?
These are local variables and not global hence other iFlows cannot be updated.
Note: iFlow ‘Analytical Reporting - Template Name - Async Fetch and Reporting’ orchestrates calls with the other iFlows via PD calls for report generation
Describe the bug
Hi - We have configured the iflow "Analytical Reporting - Template Name - Async Fetch and Reporting" for template as per the config guide.
When we deploy it, iflow is always going through route highlighted in attached ScreenShot-1. This is due to properties "AdhocJob" & "ScheduledJob" created in "Initialization" step always returning as blank. These properties created in "Initialization" step as Global Variables.
Question:
Please correct me if my understands of this iflow is wrong.
Regards,
Kishore
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
Attached ScreenShot-1
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: