I am an Enterprise Architect, coming in halfway through a project, and I'm working with an Appian platform for the first time. I have most recently worked extensively with Mendix, and I am an expert developer on that low-code platform.
Is this correct?
Having asked my very experienced lead developer a few questions, his response:
If this is truly the case, then it would appear that Appian is unable to fulfil the UX requirements of the customer, which would be a shame to discover in the second Sprint!
Any help or information would be very appreciated.
Discussion posts and replies are publicly visible
2. Yes, from developer view, all UI components are like graphical widgets.
3. If we want to fulfill the customer UX requirements, provision has been given with the help of Embedded Interfaces by Appian.
Thank you for your response! I realise that I come at this problem with experience from a 'competitor's' PoV! That is why I made the disclaimer early on ...
I was already aware of the resources to which you link. Our lead developer, who is probably the most experienced Appian developer in Germany, gave me quite a clear indication of the characteristics of the Appian UI, and I was looking for 'independent' confirmation. I am aware of the security implications of JS; I am also aware that other platforms (such as Mendix) are able to offer UI functionality through use of JS, that Appian has effectively 'closed off'. From a neutral PoV, (and I am tech neutral in this case because I'm in the role of architect / analyst working for the client, not developer), I simply want to satisfy the clients UX requirements. It would appear that the Appian platform is currently not able to satisfy those requirements according to the information I currently have. What I do find hard to believe is that a high-quality low-code platform in 2017 is unable to support basic UI techniques such as 'drag-and-drop' and 'copy-paste', where we successfully implemented this, using Mendix, in a very high security medical environment early in 2017, and passed the subsequent audit. As stated, my objective is to find a way to achieve this using Appian, because the process is already invested in the Appian platform.
Possible workarounds would be to use the same kind of 'keystroke' functionality as the Jira web application:https://confluence.atlassian.com/agile/jira-agile-user-s-guide/using-keyboard-shortcuts... this would provide very rapid workflows for our client, but I haven't been able to establish a way to make this functionality available through the Appian interface. I would be delighted to know how this could be achieved!Again - thanks for your response - I do appreciate it.
Again, thanks Malcolm.
I completely understand your point about "JS for drag-and-drop" not being standard 'out of the box' low-code functionality. But it would be nice to be able to add this functionality to our Appian project, and I am now of the opinion that it's not possible, which is a shame. I don't think it's unfair to say that I'm not the only one to see this as an opportunity for the Appian platform! :-)
As far as our current development resources are concerned, I have no doubt of their overall competence and experience. At the generic level, everything works perfectly in terms of Agile development, understanding of requirements etc.
Finally: there is no such thing as a 'perfect platform'; all have strengths and weaknesses. I found it interesting, as a developer, to compare Appian to my other experiences, and to look at it from a UML / BPMN PoV. I very much liked the fact that the development environment is fully web-enabled, which is not always the case! :-) I am looking forward to seeing how the Appian platform works in the full DTAP environment as we move into Acceptance testing.
© 2024 Appian. All rights reserved.