22.4 Feedback - major overhaul to process modeler has removed Grid Lines by default

Certified Lead Developer

First let me start this off with some good news.  The left-hand object bar has been further tweaked and reorganized.  I previously commented that "process model / interface search results" being at the top of the list (as they are in 22.3 and lower) makes it harder to access the Smart Service Nodes we're after when that's what we're actually searching for.  It looks like they listened! Yay!

But for the main point of this post: i've noticed that Grid Lines are now turned off by default and there is no way to undo this except by turning them on manually every single time you load a process model.

At first I was hoping this was a bug in my Community Edition instance, or some incomplete feature or temporary break.  But other users are now posting screenshots from 22.4 versions around community and it seems like it may have been "intentional".

Hey Appian folks?  This may have been intended to "look cleaner" or something - but to me, psychologically, it makes me think something hasn't loaded correctly.  As far as I know, with as long as I've been looking at process models with grid lines, I anticipate this effect will last a long time.

I see they're still there.  They're redesigned but I guess I don't have any major qualms with the newer, simplified grid lines (i'll paste an example below for everyone's reference).  Can we just have them turned back on by default?  Could it at least be given as an override in designer user-level preferences or something?

I know the product backlog is huge, lots of higher-priority stuff, etc.  But I think this is something that wasn't necessary to change.

  Discussion posts and replies are publicly visible

  • 0
    Certified Lead Developer
    in reply to Sam Wahbeh

    Thanks for replying to my concern.  I wonder if anyone at the Appian design team actually inquired with any regular developers to validate these ideas?

    busy process models feel less cluttered and easier to read.

    I'm doing a side-by-side comparison with one of the busier ones I have in my TEST environment.  I don't exactly agree, though of course this is subjective.

    Modernized how the overall process modeler looked

    I noticed previously that the grid lines have been simplified (no longer a lighter-colored "internal grid" in each grid element, for instance).  I'd be curious why that would be done only to have grid lines now turned off by default.  Personally I have a hard time accepting that this is a "modernization element", because I can't get around the feeling that a process model loaded with no grid feels like it didn't load completely.  Maybe others feel differently.

    I wish at least the setting would persist per designer preference and/or at least save with the state of the process model.  For those of us who like / need the feature to be "on", we're now forced to manually switch it on for each and every PM / instance we open.

    Any thoughts on the above from , , , ?

  • 0
    Certified Lead Developer
    in reply to Chris

    Would you be able to add a screenshot also showing the mouseover for a CDT property, for additional reference?

  • In the legacy expression box, it would show the data type of individual CDT fields upon mouseover (i'm pretty sure, at least.  i don't have access to a legacy instance to check this.  ?)

    Yep, in my 21.1 instance expression editors it does show both the type, and indicates a list on hover-over, for regular PVs and CDT elements:

  • I understand that not having the grid lines load can be jarring (especially when you are expecting them there). The primary driver for defaulting them off is due to the following reasons:

    • Made busy process models feel less cluttered and easier to read. 
    • Modernized how the overall process modeler looked

  • 0
    Certified Lead Developer
    in reply to Sam Wahbeh

    Also I was hoping to get some feedback on the change I discussed in my top-level post: the unannounced and now-default "turned off" behavior of PM grid lines.  One of my environments is now upgraded to 22.4 and I continue to find it ugly / kinda distracting every time I open a PM / instance in that environment.  I don't see why this default had to change, unless the change was in error - I can't imagine anyone was asking for it, or that the upcoming process modeler roadmap requires "no more grid lines" as some sort of best practice?

  • 0
    Certified Lead Developer
    in reply to Sam Wahbeh

    Yup, I did see, thanks - it was much appreciated Slight smile

  • 0
    Certified Lead Developer
    in reply to Sam Wahbeh

    In the legacy expression box, it would show the data type of individual CDT fields upon mouseover (i'm pretty sure, at least.  i don't have access to a legacy instance to check this.  ?)

    I can't remember whether it showed the array/singular setting on the PV, but it really should show that too (at least how it works in the Expression Rule editor, see below screenshot).

  • 0
    Appian Employee
    in reply to Chris

    I can't speak for all of these but when we re-added the expression editor in 22.4, we did add back the ability to mouse-over for data types + inline documentation (if available). 

    Regarding this enhancement request:
    -
    3.)  Differentiate Smart Services in the left panel by Plugin or Appian/OOTB.  This could help developers realize which plugins they are using, and look for OOTB solutions that might fit the bill first.
    -
    In 23.1 we are planning on adding a plug-in indicator to the following places:
    1. The process model icon palette (to help developers know when they are selecting an OOTB smart service
    2. Adding it to the Node dialog box (to help developers who are troubleshooting a process model)
  • What other data would you like included in the expression editor? If you do mouseover the variables we show the data type as well as the inline documentation. 

  • Hey Mike, 

    We did end up hotfixing this (AN-218956) and removed support for GIF icons in the 22.4 process modeler due to how poorly the old icons looked with the new branding. If we don't detect a properly formatted SVG icon Appian will show the default plug-in icon. 

    Plug-in Developers can follow the guidance our Appmarket team sent out if they want their icon to display.