I would like the ability to export the data from a workspace view rather than having to create a report first. Second best would be to be able to create reports that mirror workspace views (maybe even keep them linked so that a linked report always matches a particular view).
In my past experience I utilized a product very similar to PLM360 called Gael Q-Pulse.
In this system you were able to drill down any of the features by simply right mouse clicking on the chart or graph which would have options to drill down deeper.
For instance, I currently have a chart that depicts my customer complaints by defects. If I want to see what specific details are related to my top defect, I either have to create another chart or go to the customer complaints and then FIND the complaints related to the subject defect. One of these issues is that it querries the data-base for all related or defects that have the spacific word in it and may not pertain to the top defect that I am searching for.
In the system I have utilized before, allowed for a simple right mouse click with options to review the related documents or complaints that only relate to the specific bar or pie section ia am drilling down. The options were limited to what sections or fields that I have in my overview. Each drill down would also be able to drill down even further and so on. The data is there, but just needs to be created.
I generate a lot of reports and need to be able to respond to my managers the details without having to generate extensive searches etc.
I am getting pretty proficient in the charting process and have several charts in my dashboard that I use every day for tracking & reporting purposes.
The problem I have is any minor change I make in the reports section, it deletes the chart from my dashboard and I have to once again add the chart back into my dashboard. "frustrating"
I recently created multiple charts and made sure that they were working properly before publishing them and had them on mty dashboard. When I simply went into the reports and changed the report from a private to public report is once again deleted it from my dashboard even though the content didn't change. This of course happens when you make any ajdustmentsuch as change a date or chart type as well.
Why does it delete the chart from my dashboard? This is a very frustrating problem as I have multiple charts that now I have to re-upload into my dashboard and is an ongoing issue.
The system does not seem to actually be linking the reports data base to the dashboard and appears to simply be a snapshot. Refreshing the dashhboard does not update the chart as changed in the reports tab since it no longer exists in the dashboard.
I would like to suggest that this link to the reports and dashboard be actually linked. The title fields are the same and therefore the chart is getting the data from the same location. As you refresh the dashboard, it should identify those changes and simply udate the chart in the dashboard accordingly rather than seeing it as a brand new chart deleating the old chart and then haveing to bring in again.
Both for Service Requests and Sales Meetings planning would be usefull to have a kid of report called
something like Planning report showing Dates on columns(for visits, meeting, events, etc) and being able to select another field for rows and cell contents.
It would be something like what MS Excel calls Pivot Tables. I understand it may be not trivial to develop but, from the management point of view, the applications would be many. Time management is an high priority issue for all.
For instance, think about a report with dates in columns titles, technicians names on rows titles and the the scheduled customer's name, with contact's phone number and Service Request descriptions inside the cells.
In PLM360, the history of an item is available through a change log, however, the change log is not available through the API for each record in order to enable historical reporting on the actions for an item.
Use Case: changes to Product Name as it moves from temporary to legal versions.
Previously we had problems with product name changes over time because we were communicating to customers about products they didn’t buy.
We could write on every transaction into the ODS
For Ad hoc we could clone records into another workspace and store them for a historical view