Best Practices for Appian developers
Appian best practices are like a check list, use these checklists at different stages of your development cycle as described to ensure application success and reduce technical risk. Each section provides guidance for when and how often you should use these.
2.Best practices for creating CDT & Data Store :-
CDT(Custom Data Type) :-
1.Follow the naming convention as AppPREFIX_camelCase (Example: <APP Prefix>_nameCDT)
2.Provide proper description for a CDT
3.CDTs should use application-specific namespace. (Example: urn:com:appian:types:<App Prefix>)
4.The CDT name should closely match the underlying database table/view name with the appropriate format.
5.All CDTs should contain no more than 50 fields.
6.Specify column names not more than 27 characters.
7.All CDTs stored in data store should expose a primary key.
8.CDTs should not have more than 1 level of nested CDTs
9.CDT should have proper column definitions (define in XSD) in accordance with the underlying database table.
10.Avoid rename, delete or change the type of existing CDT fields.
11.Include nullable as true annotation wherever applicable.
12.When adding new fields to CDT already in use, ensure that the process models and rules using this CDT can properly handle null values in the new CDT fields.
13.Create CDT with parent child relationship by specifying the primary key element in all child tables.
14.If flat CDTs have fields that store IDs of other records, the CDTs should have foreign key constraints defined in the database schema.
15.Designers should not reuse CDTs across applications.
Data Store :-
1.All data stores should follow the naming convention with Application Prefix. (Example: <APP> My DS)
2.Provide proper security to the Data store to access the DB entities. (Admin group as administrators and All Users group as Editor).
3.Have separate data store for CDTs of tables and views.
4.Entities inside the data store should follow camel case naming convention.
No comments:
Post a Comment