• State Suggested Answer
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 7 subscribers
  • Views 27365 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Appian Best Practices Info

roopeshv1
From where we can get information related to Appian Best Practices. For 16.3 version , I found two documents ,
1. Project_Implementation_Best_Practices_Checklist
2. Standard_Object_Names

but both of them recommend different conventions for few items. For e.g.
For "RULES" naming convention
1. Project_Implementation_Best_Practices_Checklist says "All Rule names use the form PREFIX_camelCase()"
2. Standard_Object_Names says "For Rules, use pascal case"

Please assist.

OriginalPostID-267211

  Discussion posts and replies are publicly visible

Parents
  • 0
    A Score Level 1
    These are just suggestions for standard naming - it is subjective. They are not hard rules.
    Lot of projects and people use PREFIX_camelCase. For eg: APN_displayBoolean is the name of a rule from "Common Appian Rules" application by Appian.
    You can also refer the "Case Management app" created by Appian.
    It uses both camelCase and Pascal case.
    For eg: Here are few names of the rules from case management:
    CASE_APP_CustomerDiffLabelValue
    CASE_APP_createNewCustomer

    One is camel case, another is pascal case. The prefix is CASE_APP.

    So, you can use either convention. Both are fine.
    But, once you decide which convention to use, follow it throughout the development of that application consistently.
Reply
  • 0
    A Score Level 1
    These are just suggestions for standard naming - it is subjective. They are not hard rules.
    Lot of projects and people use PREFIX_camelCase. For eg: APN_displayBoolean is the name of a rule from "Common Appian Rules" application by Appian.
    You can also refer the "Case Management app" created by Appian.
    It uses both camelCase and Pascal case.
    For eg: Here are few names of the rules from case management:
    CASE_APP_CustomerDiffLabelValue
    CASE_APP_createNewCustomer

    One is camel case, another is pascal case. The prefix is CASE_APP.

    So, you can use either convention. Both are fine.
    But, once you decide which convention to use, follow it throughout the development of that application consistently.
Children
No Data

© 2024 Appian. All rights reserved.