Difference between revisions of "ProDon:Categories vs Customized Fields vs Characteristics"

From Logilys
Jump to: navigation, search
 
(37 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Header_ProDon | | 4.6.7.24 | Nadia Carrier | | 2012/07/28 }}<br>
+
{{Header_TOC}}<br>  
  
== Introduction  ==
+
'''<u>CAUTION</u>''' : This document is for '''VERSION''' '''5''' of '''''Prodon'''''. To go to the document for version 4, [[ProDon:Categories_vs_Customized_Fields_vs_Characteristics (Version 4)|click here]].
  
When designing '''''ProDon''''', general information that is necessary for the majority of organizations has been integrated, Also, the software developed to allow the users to configure and customize the options according to their specific needs.
+
<br><span style="color: rgb(255, 0, 0);">'''WARNING&nbsp;: This document is currently being edited/revised, it is possible that some parts are missing or obsolete.'''</span>
  
  
  
There are three ways to customize the different management of the software ("Client Management", "Transaction Management", "Donation Occasion Management", etc.). Depending on the future use and where the customization is necessary, one of the three methods could be more adequat. To know the situations where customizations can be used, see this section.
+
== Introduction  ==
  
 +
When designing '''''ProDon''''', general information that is essential for the majority of organizations was integrated. Also, the software has been developed to allow the users to configure and customize the options according to their specific needs.
  
 +
<br>
  
The 3 different methods to customize the system are the following:
+
There are 3 ways to customize the different management of the software ("Client Management", "Transaction Management", "Donation Occasion Management", etc.). Depending on the future use and where the customization is necessary, one of the 3 methods could be more adequate. To know the cases where customizations can be used, see [[#part2|this section]].
  
*Client categories
+
<br>
*Customized fields
 
*Characteristics
 
  
 +
The 3 different methods to customize the system are the following:
  
 +
*[[ProDon:Categories vs Customized Fields vs Characteristics#Client_Categories|Client categories]]
 +
*[[ProDon:Categories vs Customized Fields vs Characteristics#Customized_Fields|Customized fields]]
 +
*[[ProDon:Categories vs Customized Fields vs Characteristics#Characteristics|Characteristics]]
  
The first questions to ask yourself in order to find the most appropriate customization method are the following:
+
<br>
  
*For which type of information this customization is necessary? (Is it for clients, transactions, donation occasion activities, etc.)?
+
The first questions to ask yourself in order to find the most appropriate customization method, are the following:
*Is a start date and/or end date necessary?
+
 
 +
*For which type of information this customization is necessary? (Is it for clients, transactions, donation occasion activities, etc.)?  
 +
*Is a start date and/or end date necessary?  
 
*Is it possible that I need to use this customization more than once for an element? (For instance, a volunteer can have the "professional competence" in accounting, and the "professional competence" in reading.)
 
*Is it possible that I need to use this customization more than once for an element? (For instance, a volunteer can have the "professional competence" in accounting, and the "professional competence" in reading.)
  
 +
<br>
  
 +
It is also possible to conduct a [[Common functions:Search Bar|search]] or apply a [[Common functions:Filter Data (Queries)|filter]] on those customizations and to use them in [[ProDon:Custom Reports|custom reports]].
  
It is also possible to conduct a serach or apply a filter from the customizations and to use them in custom reports.
+
'''NOTE: '''It is important to know that the customization methods can be complementary amongst themselves. More than one customization can indeed be used at the same time in a single filter and it is possible to combine them to fields of the database. For example, I could search all the clients in the Toronto area (Field in the database), who are volunteers (client category) and who are available on Saturday night (Characteristic).  
 
 
'''NOTE: '''It is important to know that the customization methods can be complementary amongst themselves. More than one customization can therefore be used at the same time in a single filter and it is possible to match them to fields of the database. For example, I could search all the clients in the Toronto area (Field in the database), who are volunteers (client category) and who are available on Saturday night (Characteristic).
 
 
 
 
 
 
 
 
 
  
 
<br>  
 
<br>  
 
<br>
 
  
 
== Client Categories<br>  ==
 
== Client Categories<br>  ==
  
Only available in the "Client Management", this type of customization is actually a checkbox, a piece of information on the client that will be useful for internal purposes. That is the easiets to use, but the most limited one, since it does not allow for keeping a long-term history. It is therefore advisable to use this type of customization only if the present time is imortant. For instance, if a client is a volunteer and decides not to be one anymore, you must uncheck this checkbox. Once the box unchecked, you do not have any means to know that the client has been a volunteer in the past.<br>  
+
Only available in the "Client Management", this type of customization is actually a checkbox, a piece of information on the client that will be useful for internal purposes. That is the easiest one to use, but the most limited one; since it does not allow for keeping a long-term history. It is therefore advisable to use this type of customization only if the present time is important. For instance, if a client is a volunteer and decides not to be one anymore, you must uncheck this checkbox. Once the box is unchecked, you do not have any means to know that the client was a volunteer in the past.<br>  
 
 
 
 
 
 
Client categories are visible in the client file and can be used to retreive clients lists or filters containing one or more categories, for example, "Volunteer".
 
 
 
  
 +
<br>
  
 +
Client categories are visible in the client files and can be used to retrieve client lists or filters containing one or more categories, for example, "Volunteer".
  
 +
<br>
  
 
=== Positive and Negative Points of the Client Categories<br>  ===
 
=== Positive and Negative Points of the Client Categories<br>  ===
  
*Can be used t as filters  
+
*Can be used to create filters  
 
*'''Cannot''' be used in custom reports  
 
*'''Cannot''' be used in custom reports  
 
*'''Cannot '''be configured to be compulsory in information entry  
 
*'''Cannot '''be configured to be compulsory in information entry  
*'''Cannot '''be&nbsp; visible in management grids and are not available for search purposes  
+
*'''Cannot '''be&nbsp; visible in the management grid and are not available for [[Common functions:Search Bar|search]] purposes  
 
*'''Cannot''' keep a history of the past since it is only a checkbox
 
*'''Cannot''' keep a history of the past since it is only a checkbox
  
 
<br>  
 
<br>  
  
To learn how to create and use client categories, see the "Tab "4-Categories"" section of the "Client Management" document.  
+
To learn how to create and use client categories, see the [[ProDon:Client Management#.224-Categories.22_Tab|""4-Categories" Tab"]] section of the [[ProDon:Client Management|"Client Management"]] document.  
  
<br>
+
<br>  
  
 
== Customized Fields<br>  ==
 
== Customized Fields<br>  ==
Line 72: Line 70:
 
*A response value
 
*A response value
  
Customized fields are available in several mangement of '''''ProDon'''''. They can be created to manage information specific to:  
+
<br>
 +
 
 +
Customized fields are available in several '''''ProDon''''''s managements. They can be created to manage information specific to:  
  
 
*Clients  
 
*Clients  
*Donation occaiosn activities  
+
*Donation occasion activities  
 
*Transactions  
 
*Transactions  
 
*Expenditures
 
*Expenditures
Line 81: Line 81:
 
<br>  
 
<br>  
  
=== Positive and Negative Points of the Customized Fields<br>  ===
+
=== Positive and Negative Points of Customized Fields<br>  ===
  
*Can be used to make filters  
+
*Can be used to create filters  
 
*Can be used in custom reports  
 
*Can be used in custom reports  
*'''Cannot '''be used more than once (a customized fiels is there only once and has no response value)  
+
*'''Cannot '''be used more than once (a customized field is valid only once and has only one response value)  
 
*Can be configured to be compulsory in information entry  
 
*Can be configured to be compulsory in information entry  
 
*Can be used as merge fields in master documents  
 
*Can be used as merge fields in master documents  
*Can be visible in the management grids and are available for search purposes
+
*Can be visible in the management grids and are available for [[Common functions:Search Bar|search]] purposes<br>'''NOTE: '''To learn how to make a customized field visible in a management grid, see the [[Common functions:View Management|"View Management"]] document.
 +
 
 +
<br>
  
'''NOTE: '''To learn how to make a customized field visible in a management grid, see the "View Management" document.  
+
To learn how to create and use customized fields, see the [[ProDon:Customized Field Configuration|"Customized Field Configuration"]] document.  
  
 
<br>  
 
<br>  
 +
 +
== Characteristics<br>  ==
 +
 +
This type of customization is actually a customized field containing:
 +
 +
*A name
 +
*A description
 +
*Response values
 +
*Start date (optional)
 +
*End date (optional)
 +
 +
<br>
 +
 +
This is the most flexible customization and, in doubt, probably the most appropriate. It can also be part of a grouping of characteristics in order to add a lot of them in one easy operation.
 +
 +
<br>
 +
 +
Characteristics are available in many '''''ProDon''''''s managements. They can be created to manage information specific to:
 +
 +
*Clients
 +
*Donation occasion activities
 +
*Prospecting and commitments (requires the [[ProDon:Prospecting and Commitments Module|"Prospecting and Commitments"]] module)
 +
*Transaction batches (in the "Analysis and History" management)
 +
*Task and history
 +
*Transactions
  
 
<br>  
 
<br>  
  
<br>
+
=== Positive and Negative Points of the Characteristics<br> ===
 +
 
 +
*Can be used to create filters<br>
 +
*Can be used in custom reports<br>'''CAUTION:''' To be able to use a characteristic in a custom report, the characteristic must allow only one value per record (see point <span style="color: rgb(255, 0, 0);">'''E'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document) and must be visible in the management grid (see point '''<span style="color: rgb(255, 0, 0);">H</span>''' of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] section).
  
== Characteristics<br> ==
+
*Can be used more than once (the same characteristic can be entered more than once in order to document several response values)
 +
*Can be configured to be compulsory in information entry<br>'''CAUTION: '''To be able to configure a characteristic so that it becomes compulsory, it must first allow only one value per record (see point<span style="color: rgb(255, 0, 0);">''' E'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document), it must always be present (see point<span style="color: rgb(255, 0, 0);">''' I'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document), then it can be defined as compulsory (see point <span style="color: rgb(255, 0, 0);">'''J'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document).
  
<br>
+
*Can be visible in the management grid and are therefore available for [[Common functions:Search Bar|search]] purposes<br>'''NOTE: '''To learn how to make a characteristic visible in a management grid, see the [[Common functions:View Management|"View Management"]] document.<br>'''CAUTION: '''To become visible in the management grid, the characteristic must first allow only one value per record&nbsp;(see point '''<span style="color: rgb(255, 0, 0);">E</span>''' of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document), then it can be visible in the management grid (see point <span style="color: rgb(255, 0, 0);">'''H'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document).
  
=== Positive and Negative Points of the Characteristics<br> ===
+
*Can be used as merge fields in master documents (only the response value is entered by default, but it is possible to configure the merge field so that other elements of the characteristic are entered, for instance, the start date, the end date, etc.)
 +
*Possibility to specify a default response value, if desired
  
<br>
+
<br>  
  
== Summary of Previous Explanations<br> ==
+
To learn how to create and use characteristics, see the [[ProDon:Characteristic Management|"Characteristic Management"]] document.
  
<br>
+
== Summary of Previous Explanations<br> ==
  
{| border="1" width="50%" cellspacing="1" cellpadding="1" class="wikitable"
+
The following chart quickly demonstrates the way in which the 3 types of customization can be used and the managements in which they are available.<br>
 +
 
 +
'''CAUTION: '''Read the notes below the chart.<br>
 +
 
 +
<br>
 +
 
 +
{| width="600" cellspacing="1" cellpadding="1" border="1" class="wikitable"
 
|-
 
|-
| <br>
+
| width="43%" |
| <br>
+
| width="19%" style="text-align: center;" | '''Client Categories'''
| <br>
+
| width="19%" style="text-align: center;" | '''Customized Fields'''
| <br>
+
| width="19%" style="text-align: center;" | '''Characteristics'''
 
|-
 
|-
| <br>
+
| Check box<br>  
| <br>
+
| style="text-align: center;" | X
| <br>
+
|  
| <br>
+
|  
 
|-
 
|-
| <br>
+
| Can be used to create filters
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| Can be used in custom reports<br>  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X <br>(See note 1)
 
|-
 
|-
| <br>
+
| Can be used more than once<br>  
| <br>
+
|  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| Can be configured to be compulsory in information entry<br>  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X <br>(See note 2)
 
|-
 
|-
| <br>
+
| Can be visible in the management grids
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X <br>(See note 3)
 
|-
 
|-
| <br>
+
| Available as merge fields in master documents<br>  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| Possibility to specify a default response value<br>  
| <br>
+
|  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| colspan="4" style="text-align: center;" | '''{{Anchor||part2}}Locations where customizations can be used'''<br>
| <br>
 
| <br>
 
| <br>
 
 
|-
 
|-
| <br>
+
| Client Management<br>  
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| Task and History Management
| <br>
+
|  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| Donation Occasion<br>  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" |
 
|-
 
|-
| <br>
+
| Donation Occasion Activities<br>  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| Transactions
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| Prospecting and Commitments<br>  
| <br>
+
|  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| Batches
| <br>
+
|  
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
 
|-
 
|-
| <br>
+
| Expenditures
| <br>
+
|  
| <br>
+
| style="text-align: center;" | X
| <br>
+
|  
 
|}
 
|}
  
<br>
+
<br>
 +
 
 +
'''NOTE 1: '''To be able to use a characteristic in a custom report, the characteristic must allow only one value per record (see point<span style="color: rgb(255, 0, 0);">''' E'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document) and be visible in the management grid (see point '''<span style="color: rgb(255, 0, 0);">H</span>''' of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document).
 +
 
 +
<br>
 +
 
 +
'''NOTE 2: '''To be able to configure a characteristic so it becomes compulsory, it must first allow only one value per record (see point <span style="color: rgb(255, 0, 0);">'''E'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document), always be present (see point <span style="color: rgb(255, 0, 0);">'''I'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document), then it can be defined as compulsory (see point<span style="color: rgb(255, 0, 0);">''' J'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document).
 +
 
 +
<br>
 +
 
 +
'''NOTE 3: '''To be visible in the management grids, the characteristic must first allow only one value per record (see point <span style="color: rgb(255, 0, 0);">'''E'''</span> of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document), then it can be visible in the management grid (see point '''<span style="color: rgb(255, 0, 0);">H</span>''' of the [[ProDon:Characteristic Management#.22General.22_Tab|""General" Tab"]] section of the [[ProDon:Characteristic Management|"Characteristic Management"]] document).
 +
 
 +
<br>
 +
 
 +
<br>  
  
{{Footer_ProDon}}<br>
+
{{Footer_ProDon_Version|4.6.7.23}}<br>

Latest revision as of 14:33, 17 May 2019

Categories vs Customized Fields vs Characteristics


CAUTION : This document is for VERSION 5 of Prodon. To go to the document for version 4, click here.


WARNING : This document is currently being edited/revised, it is possible that some parts are missing or obsolete.


Introduction

When designing ProDon, general information that is essential for the majority of organizations was integrated. Also, the software has been developed to allow the users to configure and customize the options according to their specific needs.


There are 3 ways to customize the different management of the software ("Client Management", "Transaction Management", "Donation Occasion Management", etc.). Depending on the future use and where the customization is necessary, one of the 3 methods could be more adequate. To know the cases where customizations can be used, see this section.


The 3 different methods to customize the system are the following:


The first questions to ask yourself in order to find the most appropriate customization method, are the following:

  • For which type of information this customization is necessary? (Is it for clients, transactions, donation occasion activities, etc.)?
  • Is a start date and/or end date necessary?
  • Is it possible that I need to use this customization more than once for an element? (For instance, a volunteer can have the "professional competence" in accounting, and the "professional competence" in reading.)


It is also possible to conduct a search or apply a filter on those customizations and to use them in custom reports.

NOTE: It is important to know that the customization methods can be complementary amongst themselves. More than one customization can indeed be used at the same time in a single filter and it is possible to combine them to fields of the database. For example, I could search all the clients in the Toronto area (Field in the database), who are volunteers (client category) and who are available on Saturday night (Characteristic).


Client Categories

Only available in the "Client Management", this type of customization is actually a checkbox, a piece of information on the client that will be useful for internal purposes. That is the easiest one to use, but the most limited one; since it does not allow for keeping a long-term history. It is therefore advisable to use this type of customization only if the present time is important. For instance, if a client is a volunteer and decides not to be one anymore, you must uncheck this checkbox. Once the box is unchecked, you do not have any means to know that the client was a volunteer in the past.


Client categories are visible in the client files and can be used to retrieve client lists or filters containing one or more categories, for example, "Volunteer".


Positive and Negative Points of the Client Categories

  • Can be used to create filters
  • Cannot be used in custom reports
  • Cannot be configured to be compulsory in information entry
  • Cannot be  visible in the management grid and are not available for search purposes
  • Cannot keep a history of the past since it is only a checkbox


To learn how to create and use client categories, see the ""4-Categories" Tab" section of the "Client Management" document.


Customized Fields

This type of customization is actually a customized field containing:

  • A name
  • A response value


Customized fields are available in several ProDon's managements. They can be created to manage information specific to:

  • Clients
  • Donation occasion activities
  • Transactions
  • Expenditures


Positive and Negative Points of Customized Fields

  • Can be used to create filters
  • Can be used in custom reports
  • Cannot be used more than once (a customized field is valid only once and has only one response value)
  • Can be configured to be compulsory in information entry
  • Can be used as merge fields in master documents
  • Can be visible in the management grids and are available for search purposes
    NOTE: To learn how to make a customized field visible in a management grid, see the "View Management" document.


To learn how to create and use customized fields, see the "Customized Field Configuration" document.


Characteristics

This type of customization is actually a customized field containing:

  • A name
  • A description
  • Response values
  • Start date (optional)
  • End date (optional)


This is the most flexible customization and, in doubt, probably the most appropriate. It can also be part of a grouping of characteristics in order to add a lot of them in one easy operation.


Characteristics are available in many ProDon's managements. They can be created to manage information specific to:

  • Clients
  • Donation occasion activities
  • Prospecting and commitments (requires the "Prospecting and Commitments" module)
  • Transaction batches (in the "Analysis and History" management)
  • Task and history
  • Transactions


Positive and Negative Points of the Characteristics

  • Can be used more than once (the same characteristic can be entered more than once in order to document several response values)
  • Can be configured to be compulsory in information entry
    CAUTION: To be able to configure a characteristic so that it becomes compulsory, it must first allow only one value per record (see point E of the ""General" Tab" section of the "Characteristic Management" document), it must always be present (see point I of the ""General" Tab" section of the "Characteristic Management" document), then it can be defined as compulsory (see point J of the ""General" Tab" section of the "Characteristic Management" document).
  • Can be used as merge fields in master documents (only the response value is entered by default, but it is possible to configure the merge field so that other elements of the characteristic are entered, for instance, the start date, the end date, etc.)
  • Possibility to specify a default response value, if desired


To learn how to create and use characteristics, see the "Characteristic Management" document.

Summary of Previous Explanations

The following chart quickly demonstrates the way in which the 3 types of customization can be used and the managements in which they are available.

CAUTION: Read the notes below the chart.


Client Categories Customized Fields Characteristics
Check box
X
Can be used to create filters X X X
Can be used in custom reports
X X
(See note 1)
Can be used more than once
X
Can be configured to be compulsory in information entry
X X
(See note 2)
Can be visible in the management grids X X
(See note 3)
Available as merge fields in master documents
X X
Possibility to specify a default response value
X
Locations where customizations can be used
Client Management
X X X
Task and History Management X
Donation Occasion
X
Donation Occasion Activities
X X
Transactions X X
Prospecting and Commitments
X
Batches X
Expenditures X


NOTE 1: To be able to use a characteristic in a custom report, the characteristic must allow only one value per record (see point E of the ""General" Tab" section of the "Characteristic Management" document) and be visible in the management grid (see point H of the ""General" Tab" section of the "Characteristic Management" document).


NOTE 2: To be able to configure a characteristic so it becomes compulsory, it must first allow only one value per record (see point E of the ""General" Tab" section of the "Characteristic Management" document), always be present (see point I of the ""General" Tab" section of the "Characteristic Management" document), then it can be defined as compulsory (see point J of the ""General" Tab" section of the "Characteristic Management" document).


NOTE 3: To be visible in the management grids, the characteristic must first allow only one value per record (see point E of the ""General" Tab" section of the "Characteristic Management" document), then it can be visible in the management grid (see point H of the ""General" Tab" section of the "Characteristic Management" document).




Document name: ProDon:Categories vs Customized Fields vs Characteristics
Version : 4.6.7.23