You will want to name your Model so that it represents who or what type of information you are collecting. This is not the place to be specific so, for example, use party instead of client. Each Model should then contain any Variable that pertains to that Model. Using party as the example we would expect to have Variables to add names, addresses, personal identifiers, and other information specific to a given party.
Best Practices
Model names should be lower-case for ease of recognition.
Model names should be generic for reuseability. (e.g. contact or party as opposed to client or adversary)
*Slight variations might appear in visual references as we continually improve Knackly and our documentation.*
Now that you have created a Model, you will need to create an Object Variable in your Catalog to direct the Model to a specific question. The Object Variable will automatically include all of the variables added to your Model. This will be created specifically with a who or what in mind. Using party as the example you might use Client as the variable name. You will see this Variable in the App when creating a record.
Best Practices
Object variable names should be initial caps for ease of recognition and automated question prompt. (e.g. ClientInfo, AdverseParty)
Object variable names are specific to the information being collected. (e.g. Client, Adversary, Agents)
Create question prompts with the reader in mind. (e.g. Enter client information:)
*Slight variations might appear in visual references as we continually improve Knackly and our documentation.*