Forums » Interstage BPM Analytics General Discussion
Reporting on Non-worklist/non-dimension udas?
-
I have running process instances. Reports were requested for data that was not previously defined as worklist, dimension or trackable udas. Is it possible to create a new version that has these elements defined as worklist, dimension and trackable, migrate the existing instances to this new version and be able to report on them? Is there another way to accomplish what I am trying to do? Has anyone written DB scripts that would place existing values into the analytics tables?Author: Leslie Swan
Attachment: -
-
Leslie and msinghania,
UDAs which were not trackable are not kept in Flow DB.
There is no way to migrate nonexistent data.
Past UDAs only which were trackable can be collected by using Maintenance Flow Sensor.
Alternatively, if you have backup of UDA history as RDB table or Text file, you can create chart by using RDB/Text Sensor.
> Analytics has a connection past log setting that is supposed to fetch data for old instances, has anybody tried it? can we use it to fetch data once we have marked all the UDAs as worklist and trackable??
Once you marks UDAs trackable, Interstage BPM starts to store UDAs in historical database. However, past UDAs which were not marked as trackable yet are not in historical database. So, you can't get past UDAs if you weren't marked as trackable.Author: yuukitada
Attachment: -
Tada-San,
about the connection past log, my understanding was it's most useful when clients who do not have analytics, start using it and they can collect data for existing instances. Now as they do not have analytics, they wouldn't have thought about marking UDAs worklist/trackable for the purpose of analytics. Once they make changes, install analytics and run the ConnectionPastLog, they would still not get the data.
So doesn't this defeat the purpose having this functionality in the first place?
Thanks
MukeshAuthor: Mukesh
Attachment: -