Preface:
We're working on automating a workflow based on the forecast of another workflow, so the solution is to script an autoforecast and scrape the results from an SQLI.
Issue:
We found that the FE table is returning the start time 16 hours ahead of System time. System time is -4 GMT, so it's not GMT. Anyone encountered this odd timestamp in the FE table?
SELECT SESSIONTIMEZONE, CURRENT_TIMESTAMP,LOCALTIMESTAMP FROM DUAL
shows the correct -4 result:
here's an example forecast:
And the results stored in the DB:
We can convert the time, but this timestamp seems odd.