Process Display Component

Overview

When utilized with the companion Process Display Functions Plug-in allows designers to configure UIs that display process status on the process model itself to end users.

Key Features & Functionality

Provides a single component

  • displayProcess - that displays the process model and state from the JSON representation retrieved by the companion getProcessForDisplayData function provided by the Process Display Functions Plug-in.
Anonymous
  • This component seems to work fine one day and then fails the next. Any helpful tips for debugging. Anything in the log i can log for?

  • Thanks for the reply! Did not know the disabled parameter being standard, good to know. I'm guessing for the error I've been seeing is the latter, as I am a system admin. It is in a demo environment so there and there is a ton of junk in there so I feel like it is the latter. Not a huge deal either way.

  • Unfortunately if it is the same problem we really need to get support engaged because I believe that issue is in the networking layer around how component plugins in general are loaded on the client (you could confirm that by trying a simpler component plugin - https://community.appian.com/b/appmarket/posts/range-slider-component looks like a reasonable candidate although I haven't used that one myself)

    Do you have a support case number? I can see if I can help coordinate with the support team.

  • Hi John

    tried raising a support call, but the Support team are being singularly unhelpful and claim they cannot help.

    issue seems to be identical to that reported by vaskens210 with the same messages appearing in the chrome network log.

    (displayPm.svg and index.html.)

    Could you advise on a solution please

  • With s issue he was able to see that the component plugin was not being correctly accessed by looking at the network logs in chrome (in the logs it shows up as an error accessing displayPM.svg and `index.html` ~ actually the html file within the component plugin).  It turned out to be a name resolution issue in that case - If you have the same problem support should be able to help.  If not shoot me an email and I can try to help with trouble shooting.

  • Josh

    • Disabled is a standard component plugin parameter and I'm not doing any special handling of it right now.  You are correct that this is a very basic display of the process without interactivity
    • As far as Error messages - the generic error message you state is 1 of 3 issues - you don't have permission to view the process, it references an invalid process or the process references an invalid model (extremely unlikely).  In general its a development practice to hide the difference between those permission errors and invalid process errors so that users can't find some information about the existence of processes, but because these errors also are used by designers I agree it is a difficult state to deal with.  I'll consider if we can just surface that permission error up.
  • I am seeing the same issue. Can successfully retrieve the data but displayProcess is not updating the interface

  • Is there a user guide? Couple of question I have but can't find any answers in a doc:

    • There is a parameter on the display component called "disabled." It appears this controls if a user can click on the component, but I don't see any way of capturing what the user clicked or what to do with that information. Ex. User clicks an active sub-process node and we can then display that sub-process in this component. 
    • Can you include more detailed error messages? There are several process instances I have that throw an error, but I have no idea why an error is occurring. All the logs say is "an error occurred". I'm not sure if it is bad input data, permissions mismatch, etc. etc.
  • I've worked with on debugging this issue and it appears to be a configuration issue with all component plugins that they are working with support to resolve.

  • Hello,

    I have installed this plugin into our DEV environment along with the companion plugin that contains the function and when I attempt to utilize the component, nothing is displayed on the screen. I call the function to get the process data and I pass the data as is to the processData parameter in the component and the interface does not update. I imported the sample package provided in the zip file and the same thing is occurring after selecting a process instance. Is there something I am missing?

    Thank you