Process Diagram issue in Task Space (BAM) Dashboard

Hi Experts,

I am new to BAM and I am trying to crate this example https://community.emc.com/docs/DOC-8564. But when I click on a process instance id the process diagram chart displays an error message (The Process Diagram cannot be displayed. Please contact your system administrator. ) instead of the diagram.

Has anyone faced this problem?

Also when I click on that report for the diagram to be open the application server throws an error message like below.

19:10:05,879 ERROR [http-8080-6] null - DIAGRAM_ERROR_MSG
19:10:10,762 ERROR [http-8080-5] null - Process Diagram Servlet, processSvgHttp
Request: DfException:: THREAD: http-8080-5; MSG: [DM_API_E_BADID]error: "Bad ID
given: 0"; ERRORCODE: 100; NEXT: null
java.lang.Exception: DfException:: THREAD: http-8080-5; MSG: [DM_API_E_BADID]err
or: "Bad ID given: 0"; ERRORCODE: 100; NEXT: null
        at com.documentum.webcomponent.library.imaging.dashboard.diagram.Process
.getProcessXmlDefintion(Process.java:353)
        at com.documentum.webcomponent.library.imaging.dashboard.diagram.Process
.getProcessXmlDefinition(Process.java:215)
        at com.documentum.webcomponent.library.imaging.dashboard.diagram.Process
.appendExcutionDataXml(Process.java:220)
        at com.documentum.webcomponent.library.imaging.dashboard.diagram.Process
Diagram.transformProcessDiagram(ProcessDiagram.java:62)
        at com.documentum.webcomponent.library.imaging.dashboard.servlets.Dashbo
ardDiagramServlet.processSvgHttpRequest(DashboardDiagramServlet.java:114)
        at com.documentum.webcomponent.library.imaging.dashboard.servlets.Dashbo
ardDiagramServlet.doGet(DashboardDiagramServlet.java:56)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at com.documentum.web.servlet.ResponseHeaderControlFilter.doFilter(Respo
nseHeaderControlFilter.java:317)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at com.documentum.web.servlet.CompressionFilter.doFilter(CompressionFilt
er.java:108)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at com.documentum.web.env.WDKController.processRequest(WDKController.jav
a:98)
        at com.documentum.web.env.WDKController.doFilter(WDKController.java:86)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:191)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:298)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:857)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ss(Http11Protocol.java:588)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:48
9)
        at java.lang.Thread.run(Thread.java:619)
Caused by: DfException:: THREAD: http-8080-5; MSG: [DM_API_E_BADID]error: "Bad
ID given: 0"; ERRORCODE: 100; NEXT: null
        at com.documentum.fc.common.DfException.newBadIdException(DfException.ja
va:28)
        at com.documentum.fc.client.impl.session.Session.getObjectManager(Sessio
n.java:783)
        at com.documentum.fc.client.impl.session.Session.getObject(Session.java:
844)
        at com.documentum.fc.client.impl.session.SessionHandle.getObject(Session
Handle.java:583)
        at com.documentum.bpm.utils.ProcessDesignManager.getProcessXMLDocument(P
rocessDesignManager.java:69)
        at com.documentum.webcomponent.library.imaging.dashboard.diagram.Process
.getProcessXmlDefintion(Process.java:337)
        ... 29 more
19:10:10,762 ERROR [http-8080-5] null - DIAGRAM_ERROR_MSG

Find more posts tagged with

Comments

AlexanderL

Imran

Do you get a message from PRS (smthng like that "Select an appropriate field in the datasource tab: Process Instance Id") when you are trying to configure drilldown for procId column?

Imran_Yusubov

Yes,

I had included "Process Instance Id" form activity execution.And when I try to create a drill down I PRS had been showing a wringing message something like "choose an appropriate column from data source tab".Then I included "Process Instance ID" from "Process Execution" and it worked.I wonder wy it did not work in "Activity Execution" since they are the same things.

ArunSelvaraj

Hi Imran,

I have faced the same issue and i solved it by the following way.

Hope that you have followed all the steps correctly as mentioned in the https://community.emc.com/docs/DOC-8564 .

Assume that an report has been created using PRS and published and it is mapped in some dashboard in Taskspace.
If we did some update on the same report in PRS after mapping with dasboard.(For Eg: If we have changed drill down or changed some filter expression or changed labels for any column and again publishing the report)
We should edit the dashboard which we mapped the report. And remove the specific report from dasboard pane and freshly by dragging add it again and save.It will work fine.
Each time whenever we getting the error (Please contact your system administrator) do the same as above it wil be same for all kind of reports.

Hope it helps