Custom UX Implementation?

RE: Custom UX Implementation?

krishnay0001 — Wed, 01 Jul 2020 09:27:35 GMT

Layout means design specific to an organisation which has colors,fonts,css,pattern library created to leverage across entire organisation. If i understand, we should recreate the same in Appian designer only by using existing templates. Am i right?

RE: Custom UX Implementation?

Mike Schmitt — Tue, 30 Jun 2020 12:28:20 GMT

What exactly do you mean by "a layout"? Is that a specific type of file, etc?

Appian's interfaces don't really utilize anything I'm aware of that you could "port" from an unrelated system. That said, the design elements are fairly flexible and will allow you to tailor your Appian UX to at least feel 'familiar' to users used to an organization's design scheme on other websites.

RE: Custom UX Implementation?

krishnay0001 — Tue, 30 Jun 2020 12:20:04 GMT

I have a similar questions on the out of box layout designed for my organisation.Assume that i already have a layout designed for my application and now organisation is going for Appian , how can get my existing layout ported into appian while i update or change my workflow? I understand applan provides multiple layouts ,but you should also think of migrations in such case. Any help?

RE: Custom UX Implementation?

Peter Lewis — Wed, 03 Jun 2020 14:55:57 GMT

Ah gotcha - if you're wondering about validations in general, there's a ton of options for providing validations on any input field. Here's an example of using multiple validations in a single field. You can also use any of the library of functions to create the necessary validation.

RE: Custom UX Implementation?

prasadk0004 — Wed, 03 Jun 2020 14:36:04 GMT

Thanks Peter your reply. I am using trail version, I don't see any admin console in that. For example I said that password validation, in lot of fields validations involves the pattern validation like email, phone number etc.,

RE: Custom UX Implementation?

Peter Lewis — Wed, 03 Jun 2020 13:12:47 GMT

Where is this password being used - is this for logging into Appian? If so, there are several options for validations on passwords in the Admin Console.

RE: Custom UX Implementation?

Stewart Burchell — Wed, 03 Jun 2020 09:28:28 GMT

I'm not sure why you're implementing a password field when Appian already provides security for you? But, putting that aside for the moment, your best option is to install the RegEx functions plugin and write an expression rule that will test the value entered by the user to see if it matches the required pattern. If you're not familiar with Regular Expressions you can usually find a pattern string to use by searching the internet.

RE: Custom UX Implementation?

prasadk0004 — Wed, 03 Jun 2020 09:23:22 GMT

Thanks for your quick reply. Could you please explain If I need a validation on password fields it needs to match a pattern. I didn't any SAIL field property to perform validation using a pattern. Appreciate your help.

RE: Custom UX Implementation?

Stewart Burchell — Wed, 03 Jun 2020 08:14:20 GMT

The power of Appian to deliver solutions rapidly relies in part in restricting the options and decisions that a Developer might have. Too many choices can paralyse the delivery or slow it down significantly. My strong recommendation would be to work with your UX team to educate them in what the current set of choices are that Appian's SAIL offers and work in partnership with them to deliver the optimal UX in the shortest possible time.

Regarding validation logic - Appian provides validation capability within SAIL at the field, section and form levels so you do not need to inject any further logic.