Difference between revisions of "ProDon:Categories vs Customized Fields vs Characteristics"
Line 103: | Line 103: | ||
== Characteristics<br> == | == Characteristics<br> == | ||
− | This type of customization is actually a customized field containing: | + | This type of customization is actually a customized field containing: |
− | *A name | + | *A name |
− | *A description | + | *A description |
− | *Response values | + | *Response values |
− | *Start date (optional) | + | *Start date (optional) |
*End 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 single operation. | ||
− | + | <br> | |
− | |||
− | |||
− | Characteristics are available in | + | Characteristics are available in many of '''''ProDon''''''s managements. They can be created to manage information specific to: |
− | *Clients | + | *Clients |
− | *Donation occasion | + | *Donation occasion activities |
− | *Prospecting and commitments (requires the "Prospecting and commitments" module) | + | *Prospecting and commitments (requires the [[ProDon:Prospecting_and_Commitments_Module|"Prospecting and commitments"]] module) |
− | *Transaction batches | + | *Transaction batches |
− | *Task and history | + | *Task and history |
*Transactions | *Transactions | ||
Line 131: | Line 131: | ||
*Can be used as filters<br> | *Can be used as filters<br> | ||
− | *Can be used in customized | + | *Can be used in customized fields''' 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> oh 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). |
*Can be used more than once (the same characteristic can be entered more than once in order to document several response values) | *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 | *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<span style="color: rgb(255, 0, 0);">''' E'''</span> of the ""General" Tab" section of the "Characteristic Management" document), it must always be present (see point<span style="color: rgb(255, 0, 0);">''' I'''</span> of the ""General" Tab" section of the "Characteristic Management" document), then it can be defined as compulsory (see point <span style="color: rgb(255, 0, 0);">'''J'''</span> of the ""General" Tab" section of the "Characteristic Management" document). | + | '''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). |
− | *Can be visible in | + | *Can be visible in the management grids and are therefore available for [[Common_functions:Search_Bar|search]] purposes |
− | '''NOTE: '''To learn how to make a characteristic visible in a management grid, see the "View Management" document. | + | '''NOTE: '''To learn how to make a characteristic visible in a management grid, see the [[Common_functions:View_Management|"View Management"]] document. |
− | '''CAUTION: '''To become visible in the management grid, the characteristic must first allow only one value per record (see point '''<span style="color: rgb(255, 0, 0);">E</span>''' of the ""General" Tab" section of the "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 | + | '''CAUTION: '''To become visible in the management grid, 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). |
− | *Can be used as merge fields | + | *Can be used as merge fields in master documents (only the response value in 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 | *Possibility to specify a default response value, if desired | ||
<br> | <br> | ||
− | To learn how to create and use characteristics, see the "Characteristic Management" document.4 | + | To learn how to create and use characteristics, see the [[ProDon:Characteristic_Management|"Characteristic Management"]] document.4 |
== Summary of Previous Explanations<br> == | == Summary of Previous Explanations<br> == |
Revision as of 11:30, 28 July 2012
Contents
Introduction
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.
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.
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 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 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).
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 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 unchecked, you do not have any means to know that the client has been a volunteer in the past.
Client categories are visible in the client file and can be used to retrieve clients lists or filters containing one or more categories, for example, "Volunteer".
Positive and Negative Points of the Client Categories
- Can be used t as filters
- Cannot be used in custom reports
- Cannot be configured to be compulsory in information entry
- Cannot be visible in management grids 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 management of ProDon. They can be created to manage information specific to:
- Clients
- Donation occasion activities
- Transactions
- Expenditures
Positive and Negative Points of the Customized Fields
- Can be used to make filters
- Can be used in custom reports
- Cannot be used more than once (a customized fields is there only once and has no 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 single operation.
Characteristics are available in many of 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
- Task and history
- Transactions
Positive and Negative Points of the Characteristics
- Can be used as filters
- Can be used in customized fields CAUTION: To be able to use a characteristic in a custom report, the characteristic must allow only one value per record (see point E oh the ""General" Tab" section of the "Characteristic Management" document) and must be visible in the management grid (see point H of the ""General" Tab" section of the "Characteristic Management" section).
- 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 visible in the management grids and are therefore available for search purposes
NOTE: To learn how to make a characteristic visible in a management grid, see the "View Management" document.
CAUTION: To become visible in the management grid, 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 ^^ProDon:Characteristic_Management#.22General.22_Tab|""General" Tab"]] section of the "Characteristic Management" document).
- Can be used as merge fields in master documents (only the response value in 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.4
Summary of Previous Explanations
The following chart quickly demonstrates the way in which the three 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 as filters |
X |
X |
X |
Can be used to create 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 |
Situations where customizations can be used | |||
Client Management |
X |
X |
X |
Task and History Management |
|
|
X |
Donation Occasions |
|
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 grids (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 ballow 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