naming rule input

RE: naming rule input

erikb0001 — Wed, 17 Jun 2020 19:00:42 GMT

Hi Stewart,

Thanks for your answer, I know what to do.

Kind Regards,

Erik

RE: naming rule input

Stewart Burchell — Wed, 17 Jun 2020 09:39:36 GMT

Hi Erik - the thing about best practices/standards is that you should just have some and then stick to them. So it doesn't really matter. Camel Casing is typically used so that you can more easily read the names of variables, so I use Camel Casing in my CDT variable names EXCEPT where the variable is a Primary Key or a Foreign Key where I use Pascal Casing (again, it's all about how useful it is for humans to read and effectively assimilate the information you want to convey)

RE: naming rule input

erikb0001 — Tue, 16 Jun 2020 16:37:58 GMT

Thanks you, is it best practice tot name the variabele camelcasing, of should i user camelcasing voor the variabele insider the CDT and use the prefix underscore naming for the "object" vehicle?

The Guise says:

First, rename the auto-created rule input to align with best practices for naming variables. Click on

VFM_Vehicle, and rename it to vehicle

But as the instructions proceeds it turns out that in the instructions example the variabele was not renamed. Because of this I am not sure if the renaming is best practice.

Kind Regards,

Erik

RE: naming rule input

TJ — Tue, 16 Jun 2020 00:02:42 GMT

AFAIK, Appian is asking you to rename your CDT to VFM_Vehicle and not the variable name. You can choose to use 'ri!vehicle' as the name of your variable.