Search Results

If users need to send emails with a different email address or display name, ChilliDB Message Profiles allow this activity to be performed. As ChilliDB users may have the need for one or more Message Profiles to be associated with their user login, setting up message profiles allows them to specify/change the name that is displayed to the recipient of any emails they send - for example, "Sales" (sent from sales@yourorganisation.com); "Support" (sent from support@yourorganisation.com); "Eduaction" (sent from education@yourorganisation.com) and so on. Users can also create different message profiles for the different forms of communication they use - e.g.: Email, SMS, Fax). The following steps outline how to setup a message profile and send an email to someone using that profile. 1. Login to ChilliDB and navigate to "Preferences" 2. Select "Maintain Email Preferences" 3. If there are existing message profiles, they will be available in the Message Profile List. To add a new message profile, click “Create”. Doing so reveals a pop-up window where users can fill in the details for the new profile. 4. Fill out the message profile details. In this case, this profile will enable emails to be sent from the “Chairman”, so the “Sender Address Display Name” will be set to “Chairman”. The “Sender Address Display Name” is the name which is used when setting the Sender’s name for any messages sent through ChilliDB from this profile. This message profile will be named “Chairman”. Each message profile can have its own signature and use a different email address. When finished, click “Save” to save the changes. 5. The new message profile will now be listed, and it will also be set as the default profile. If users have more than one message profile, they can nominate one as the default, which will then be pre-loaded into the Send Message screen. 6. To test the message profile, click Send Message in ChilliDB to create a new message. If users only have one message profile, then the Send Message window will automatically display that profile, and the functionality to switch between profiles is disabled. The following image shows the signature of the message profile created above loaded into the Send Message window. The recipient’s name has been masked in this image for privacy. If you have more than one profile, you will see a “Select Profile” option under the Actions menu. Clicking “Select Profile” will introduce a new drop down to the Send Message window which shows a user's profiles and allows them to switch between them. When switching between message profiles, users can see that the content of the editor changes to match the signature of the message profile. 7. When finished entering the details for a new message, select “Send” to send it to the recipient(s). When the message arrives, the recipient will see that it is from “Chairman” intended.

The ChilliDB home screen can be configured with several "panels" which can perform basic functions related to the rest of the system and display stats and graphs important to a user's role. These panels can be configured by each user to suit their own needs and preferences. To configure these panels, click on the User Profile in the top right-hand corner of the screen, then select the "Preferences" link. This opens a new page, from which we select the 'Manage Screen Layout' link. On the Manage Screen Layout page users are presented with the home screen configuration controls. These will allow them to specify which panels are shown and which are hidden, defining the layout which will be visible on the home screen. All Visible Panels are displayed as a box which sits in one of five areas (the top and bottom sections organise panels vertically down the screen; the middle section organises them horizontally in 3 columns). To edit the layout, a panel that is to be visible should be dragged to the area it is to be displayed it in. Any panel in the Hidden Panels section cannot be seen. Once the settings meet the user's needs, they click the “Save” button at the bottom of the screen to save them. The results of any changes can be viewed by clicking the logo on the top left of the screen (usually the company logo

ChilliDB offers a number of ways to personalise your system so you can work more effectively. Most of these are located in "Preferences" in the user menu, which is accessed by clicking on the user’s initials on the top right of the screen. Explore 7 ways to personalise your ChilliDB system by reading below! Manage Screen Layout Users can customise their dashboard layout in ChilliDB so they have the data they need to access most regularly at hand when they log in to the system. To do so, navigate to User Profile, select Preferences, and then click on "Manage Screen Layout" to rearrange the layout of the home page. It is the possible to easily drag and drop the different modules from the Hidden Panels section into the Visible Panels grid. Note: The Visible Panels grid has three sections - the top and bottom sections arrange the panels vertically down the screen. The middle section allows users to arrange panels in 3 columns across the screen, allowing for greater visibility. To view more about altering the screen layout view our article here. Set Up Email Profiles Another way users can save time is by setting up multiple email profiles so they can easily send a message on behalf of another employee. This is done by navigating to User Profile and selecting Preferences (the same process as the Manage Screen Layout section above). Then click on "Maintain Email Preferences". Learn more about this process in our article here. Turn On Prompt Panels The Assist Prompt Panels usually only appear the first time users access a module. This can be turned on permanently in User Profile under "Preferences - Maintain User Preferences" to get step-by-step tutorials in relevant modules. Access Our Help Guides Turn on User Rules so they appear when the "Help" button is clicked in applicable modules. Customise The Menu Order Personalising the menu order allows users to save time searching for menu items they use everyday. For more information check out our article here. Set Default Types For Modules Save time by setting default types for Contact, Organisation and Case Management modules so new data can be entered quickly. Learn how to set up default values through our article here. Pop Up Alerts Be immediately informed of any changes in ChilliDB by turning on Pop Up Alerts in User Profile under "Preferences - Maintain User Preferences" to receive a notification as soon as someone has submitted a form, and so on.

ChilliDB users are able to enter a number of secret questions via their User Profile to aid them in recovering their password should they have any issues. To do so, click on your User Profile and choose ‘Preferences’ from the drop down menu. Then choose ‘Change My Secret Question’ from the options presented on the following screen. Users are then prompted to provide three secret password recovery questions along with answers to these questions.

If users need to set up a new password, this can be done via their User Profile and the Preferences screen. After clicking on ‘Preferences’, choose ‘Change My Password’ from the options presented on the following screen. Users are then able to change their ChilliDB system password.

Each year users should create their new membership packages for the year ahead. When doing so it is possible to import members (prospects, members, and even cancelled members if necessary) from one or more existing membership packages to save time. They will initially import as prospects, and users would then proceed to contact these prospects and carry out the necessary business steps to convert them to members for the following year. 1. Once the membership package for the new year has been created, users can click on the 'Import Members' link on the Member Details page begin the process of importing members from one or more of the previous years’ membership packages. Members can only be imported as prospect members. 2. Select the membership package from which to import members from the 'From Package' drop down list. 3. Check the Include “Cancelled” Members checkbox to import cancelled members from the selected package. 4. Click the Import button to complete the process. 5. All selected contacts will be shown as Prospects on the Membership Details display screen

If users choose to automatically generate distribution lists for a membership package, they can send electronic communications, such as email, through ChilliDB to those contacts. 1. To view the available distribution lists, navigate to the Display Distribution Lists screen, available within the Utilities main menu item - click on Utilities, then on Distribution Lists and select Maintain. 2. To filter the distribution lists so only those related to memberships are shown, select the Filter option on the top left-hand side of the screen (the default is Show Current). Then choose 'Membership' from the Categorisation drop-down list. 3. Click the 'Display' button to show all distribution lists of Type 'Membership'. Users may also filter the list by: a. Category or Sub Category b. Current, or Expired lists 4. The Distributions List grid displays the name of each membership list down the left-hand side of the page. The lists are divided into one list for Members and one list for Prospects, displayed one after the other in the list. A brief overview of the total membership for each package (also divided into contact members and organisation members); and a shortcut to member details is also displayed on this page.

Once a survey invitation has been sent to a contact, organisation and/ or distribution lists in ChilliDB, users may wish to send a reminder to ensure the survey is completed in within the desired timeframe. The 'View' filter above the grid can be used to filter the invitations to those who have not yet started the survey; those who haven't submitted it; or both. To send a survey reminder to a recipient: 1. Click in the checkbox next to the recipient to select them from the “Survey Invitation List” in the Invitations tab on the Survey Display page. 2. Select Actions > Send Reminder. 3. The 'Refine Recipients of the Reminder' pop-up window will appear to validate the chosen recipients. Users can change the contacts displayed by changing the Filter on the top left-hand side of the window. The default setting is display 'All' contacts originally invited to do the survey. However, there is the option to change this to 'Those with No Address Available'; 'Those with an Email Address'; or 'Those with an SMS Number'. Click 'Continue' if recipient details are correct. 4. A Send Message pop-up box will display. Complete all mandatory fields such as To, Subject, and Categorisation. Users may add additional recipients by clicking “Find” next to the “To” field. Follow the prompts to add additional recipients. 5. Next, users need to enter the content for their reminder. They have two options here: i. Create Your Invitation Content now Enter the desired content into the HTML Content and Plain Text Content sections of the form. Plain Text Content is for those recipients who do not receive HTML emails, who generally don't number many. It is best to copy the content from the HTML field into the Plain Text to enable recipients receive the reminder, regardless of how they read their email. Users will need to copy the link from the existing content so their recipients can use this link to access the survey. If the existing content is lost, users can use the Mail Merge Tokens and select the 'Survey' token. OR ii. Use a Message Template Select Action > Use Template. Click checkbox for the template to be used, then click 'Load'. This will now populate the email reminder with the template. Users can view a template by selecting the Template Name. They can use the 'Create Like' link to duplicate an existing template, then make changes and save it to use. They can 'Load' an existing template. They can 'Overwrite' an existing template with the content back in the Send Message window to use again in future. For this example, we have selected 'Load' to load a template. The Send Message screen will confirm that its content is to be replaced with the content from the template, and when this is confirmed, it will then load all of the content from the template into the Send Message screen. Message templates also include Subject and Categorisation fields, so the whole screen can be adjusted to a user's needs. 6. Test your message! If you use 'Send Test' from the Send Message screen and try send it to your own organisation, there will be issues when ChilliDB attempts to pre-populate the survey. The sent test in this scenario is only useful to review a message template until a user is happy with it. To test the defaulting of information into a survey, users need to create a test contact or organisation in their system and actually send the invitation to that contact or organisation. 7. Once users are happy with their reminder, click 'Send'. The reminder to complete a survey has now been sent to the chosen respondent(s).

ChilliDB surveys can be implemented in several ways - they can be sent to a contact or organisation to fill out; they can be filled out by a staff member who is conducting the survey over the phone, or in a meeting; or they can be conducted via a link on a user's website which captures anonymous responses. Send Survey links (Invitations) Once a Survey has been published, invitations can be sent to contacts, organisations and distribution lists in ChilliDB. Users can also use the contact and organisation Search pages in ChilliDB to perform a search of their database, and then select 'Send Survey' from the Actions menu for the Search Results list to send surveys. Basic Rules Only Surveys which have been “Published” can be selected for use. Only Surveys which are available (Survey Availability From / Survey Availability To) can be selected for use. This section will discuss the mechanics of sending a survey invitation. Follow the below steps to send an invitation to participate in a survey: 1. Click on the 'Invitations' tab on the Survey Display screen. 2. Click on 'Create' link to search for respondent(s). A “Find Respondent(s)” pop-up box will display. 3. Use the radio button options to select the search criteria. Depending on the security options users choose for their survey, these radio buttons and filters can behave differently. For instance, if they have a login defined for the survey, then this search will return only contacts with an external user login. Once the search criteria has been entered, click 'Search'. 4. A list will populate in a drop down box. Click on the chosen respondent and then click 'Select'. This respondent will now appear in the “Survey Invitation List”. 5. Click in the checkbox next to the respondent's name and then click Actions and select 'Send Invitation' from the dropdown list. A “Refine Recipients of the Message” pop-up box will display. 6. Check the details of the recipient(s) and click 'Continue' if everything appears to be as it should. This screen allows users to choose the communications addresses for their recipient(s). If the recipient does not yet have a communication address, one can be added here against their contact or organisation record. A recipient can also be removed if necessary. 7. Next, a 'Send Message' pop-up box will display. Complete all mandatory fields, such as To, Subject, and Categorisation. Additional recipients may be added by clicking “Find” next to the “To” field and following the prompts. 8. Users then need to enter the content for their invitation. They have two options here: 1. Create Invitation Content now Enter the necessary content into the HTML Content and Plain Text Content sections of the form. Plain Text Content is for those recipients who do not receive HTML emails, which usually do not number that many. It is best to copy the content from the HTML field into the Plain Text so the way your recipients receive the invitation can be controlled, regardless of how they read their email. Users will need to keep the link part of the existing content so your recipients can use the link to access the survey. If the existing content is lost, users can use Mail Merge Tokens and select the 'Survey' token. OR 2. Use a Message Template Select Action > Use Templates. When the Message Templates popup appears with a listing of all message templates in the system, click the checkbox for the template you wish to use, then click 'Load'. Clicking on the template name allows users to review the message template to decide if it is the one they are looking for. When the 'Load' link is selected, the message template selected will populate the email invitation with the template Users view a template by selecting the template name. They can use the 'Create Like' link to duplicate an existing template, then make changes and save it to use. They can 'Load' an existing template. They can 'Overwrite' an existing template with the content back in the Send Message window to use again in future. For this example, select 'Load' to load a template. The 'Send Message' screen will confirm that a user wants to replace its content with the content from the template and then load all of the content from the template into the 'Send Message' screen. Message templates also include 'Subject' and 'Categorisation' selections which, if chosen, change the layout of the screen. 9. Test your message! If users select the 'Send Test' option from the Send Message screen and attempt to send it to their own organisation, it can lead to unexpected results when it tries to pre-populate the survey. The sent test in this scenario is only useful to review the Message Templates until users are happy with it. To test the defaulting of information into a survey, users need to create a Test Contact or Organisation in their system and actually send the invitation to that contact or organisation. 10. Once you are happy with your Invitation, click Send. Your invitation to complete a Survey has now been sent to your chosen respondent(s).

Whilst building the survey layout and questions, it is possible to preview a survey before sending it to respondents. Users can preview the Survey Header and Footer; the Sections, Questions and Layout; and any templates they may have used when creating the survey. This preview displays the survey exactly as respondents will view it. To preview a survey select Preview from the Action menu on the top right-hand side of the Survey Display screen, as below. A pop-up box will then display a non-editable preview of the survey. To close the preview pop-up display box, click the red X in the top right corner. The survey preview will display similar to the below example:

Creating Headings and Text Content To start adding structure to a survey, users first have to navigate to the Questions tab on the Survey Details page. This is where any Questions, Headings and Text elements, along with the structure of a Survey, can be added. To begin adding new items, first right-click on the 'Questions' heading underneath the Questions tab and choose the applicable option. You can add items at a group or individual level. The options available to users by right-clicking on the 'Questions' heading are as follows: For the purposes of this example, we will start by defining some Headers and the Introduction Text for our survey. To do this, right-click on the 'Questions' heading with the Questions tab and choose 'Add Header or Text'. Then, when the edit screen appears, choose Header 1 to add this style of header to the survey. The Content box will change depending on what is selected for the Type to give you more control over the presentation of the content. Choose 'Text' and we will add some introduction text to our Survey. Note: I have chosen to style my text here for the introduction. You will see this a lot through the Survey module. You can either style up the text directly when you create it, or you can utilise the styles defined in your Template to control the look of your survey. If you do not get the option to format the content when creating it, then it is solely governed by the Survey Template. See Using Survey Templates to learn more about using styles. I have left my Survey Template Styles fairly basic, and chosen to style the text here. Creating Questions Questions are created via the Questions tab on the Survey Details page. As a user adds questions, the structure of their survey will be presented in the Questions tab as a tree view so they can see the hierarchy and branching as they create their survey. In order to add a question, right click on the Questions heading at the top of the tree to get started. When a user does this, a drop down list appears in the Questions section, from which they choose 'Add Question'. Note: You can either add an individual question on its own, or add Question Groups/ Sections first and then add questions. These questions groups/sections/questions will be presented in a hierarchical structure in the tree view beneath the Questions heading. You will then be presented with the following screen: Stepping through the Create Question screen, various decisions can be made about the Question look and feel; types of questions; if they are to default information from ChilliDB; if they have a merge strategy in place, and so on. Let's look at the features on this screen one-by-one: Question Text is where users can customise the questions in their Survey. This field uses a rich text editor, and when the mouse is hovered over it, a menu with options such as bold; a colour palette and so on, will appear so users can customise the question text. Question Suffix – can be used to include a comment related to that question. For example, “Service Name may not be the same as Legal Trading Name”. Question Help – is used to provide helpful content to a user. For example, to explain something in more detail. This option produces a help icon on the survey next to the question it relates to, which will only be visible when users hover their mouse over the icon. Internal Labels - if users want to use reporting tools such as Crystal Reports to generate reports for their surveys, then they should use internal labels to give each question a succinct, logical and short name, which can then easily be identified in reporting views and used in Crystal Reports. The reporting views for a survey allow users to easily work with the survey, and they are generated when a survey is published. The Survey Name and Section Name will help you identify the reporting views related to a survey. Default From Fields - This is one the most powerful features of ChilliDB Survey. If users want to default information from within ChilliDB into the Survey itself, they can do so from either Contact or Organisation levels of ChilliDB, and nearly all types of fields in ChilliDB can default information into your Survey. In our example, we will default the question Your Service Name to the Organisation Name in ChilliDB, so when a Survey Responder looks at the survey, their Organisation Name will be pre-filled. Response Type - When a question is defaulted to draw information from ChilliDB fields, which is being done in this example, then the rest of the question specifics are locked down. If the field in ChilliDB is a Text field, then ChilliDB survey will not let a user change the Response Type (the field / data type for your Question) to something like a Date, as that would not make sense and could create data quality issues. ChilliDB will take care of this for you. ChilliDB will also set properties such as Minimum Number of Characters, and Maximum Number of Characters along with Response Required. In the example, we can see this has been done to align with the fields in ChilliDB and to again enforce data quality to information being entered into ChilliDB. While most of the response types above are logical, some are special, for example: File – allows users to attach one or more files in their survey response Live System Data – sometimes users might want to have the survey link an existing contact or organisation in ChilliDB, rather than using plain text fields to enter a name. This option will allow the survey responder to perform a search to find a Contact or Organisation within ChilliDB. When users choose one of these options, they will be asked to choose a Data Source, similar to when creating Custom Fields. Formula – Users can construct a formula to calculate something based on information supplied by the Survey Responder, and the Formula field will present the information in the Survey – an example may be a score for something, or a GST calculation. Auto Merge On Submission – Allows users to decide on a merge strategy for each question, which has been defaulted from ChilliDB information. They can decide if the question is merged back into the ChilliDB field automatically when the Survey Responder submits their survey, or if they would prefer to review the survey response and choose to merge it manually. Automatic merge only occurs when the survey response is submitted and not when it is simply saved. Auto Merge is a separate license, so if you do not have this license, you will not see the option in your ChilliDB. To obtain the license, contact the ChilliDB HelpDesk via helpdesk@chillidb.com Response Required – This controls whether or not the question is mandatory for the survey responder. Display Annotation Field – This allows users to capture additional related information in an Annotation field, which will be displayed to the respondent as part of the question. For example, the question could be “If you answered 'No', then please explain further”, and the Annotation field could be used to capture that explanation. This option can be set if this question is a required field, or if the question needs a mechanism for recording an additional “Annotation” text or even for uploading a file. Read Only – This field is useful when defaulting information from ChilliDB in situations where you would like to just display the value and not allow the survey responder to change it. An example of this might be the Service Name. Read Only Questions are also useful for Visibility Filters, Cross Validation, and sources of data for Formula fields. Visible – This allows users to bring information into the Survey through Defaulting - for use in Visibility Filters, Cross Validation, and sources of data for Formula fields, but not have it shown to the Survey Responder on the Survey. Answer Field Position – Allows users to set the position of the answer field in relation to the question text. Once users have completed a question and decided on the relevant options, they can either create another question immediately after this one by selecting 'Next Question', or they can simply save the current question and return to the Survey Overview screen by selecting the 'Finish' button. Creating Question Groups Sometimes users may wish to ask several questions which share a common set of choice values. In this case, rather than creating each single question with a choice response type, they can create a single Question Group item for this type of questions. For example, they might be looking to capture something like this: In order to create a Question Group item, users will need to select 'Add Question Group' from the drop-down list that appears when they right click in the Question tab. They will be presented with the following screen: The detail which needs to be added to create the Question Group item is: 1. Add text in the Title to define the question. 2. Select the Type, ChilliDB will default to 'Static' answers. If users choose 'Dynamic', this is like using “Default From” on simple questions. They don’t get to choose any other options, as below: The subsequent items in this section of the document only apply to Static Question Groups. You can add a static question group, and then each question in that question group can Default to something else. 3. Users can select the choice values for their answer within the Choice Items section. With these choice values, you can add new choice; edit or delete existing choices; and arrange choice order. 4. Users can add a set of questions which make use of the choice values defined above as the answer type. With these question items, you can add a new question, edit or delete existing questions, assign a default value for each question according to the choice values defined above, and arrange the question order. 5.Once users have completed building their Question Group item, they click the 'Save' button to save the current item, and they are then returned to the Survey Display screen. When a question or question group item has been added to the survey, the Questions: Section will be displayed in a similar way to the example below: Please note as many Question and Question Group items as needed can be added to a survey. In addition to questions, there are other features that can be used to set the display/ print layout of a survey: Dynamic Question Groups - This option allows users to default Custom Field Grid Layouts into a survey. This means they can capture many “child” records for their Custom Field Grid Layout through their surveys. When defaulting to fields in ChilliDB, most things that can be changed are locked down to protect data quality. Creating Layouts to Hold Related Questions Users can place one or more Questions or Question Group items into rows and columns; group them with a border; show grid lines, or a combination of these, by selecting 'Add Layout Item' from the drop down list in the Questions section. When doing so, they will be presented with the following screen: On this screen, users can choose if they would like to have vertical or horizontal grid lines within the layout; set a colour for the grid lines; choose the thickness of the grid lines; and how many columns per row do they want to have within the layout. “Fieldset” is another important item - this is what draws the box around the collection of Questions in the Layout to make it look nice. Once users have completed the settings in their Layout Item, they click the 'Save' button to save the current item and return to the Survey Display screen. The Layout Item section also provides the ability to add feature items, such as a question, into this section. This is done either by using the cursor to drag the chosen question into the layout section; or questions can be added to the layout section by right-clicking on the Layout Item and then selecting Add Question/or Add Question Group from the drop down list. In order to insert a question/ question group item, the same process is followed as when creating a Question/ Question Group item for the survey. Users can also create this layout recursively, which means they can create a layout within a layout. There is no limit on how many recursive depths are used within this layout item. Re-Sequencing Survey Elements Once users have added a number of Questions, Layouts, Sections etcetera, they can easily re-sequence their survey by dragging these items up and down in the Tree View to restructure the survey. Some items may also be dragged underneath other items to create the nesting of items, where ChilliDB supports this option. Not all elements can be nested, and ChilliDB will guide users when they try to do this. Visibility Filters Visibility Filters are available for sections and layouts (from 3.2 onwards). When creating or maintaining a section or layout, users may define one or more visibility filters, which control the visibility of all questions within the relevant sections or layouts. This is a useful tool for conditionally showing only part of a survey and having conditions based on information either entered by the survey responder, or based on information a user has defaulted into the survey itself. An example of where this would be used is if a user has a collection of questions which are defaulting information from within ChilliDB for organisations. These organisations have Custom Fields Sections which are relevant to certain types of organisation. For example, a Custom Fields Section called 'General Practice Details', which would be collected for organisations of the type 'General Practice'. A visibility filter would allow users to only collect information from those survey responders who are from organisations of this type for that part of the survey. To achieve this, users add Visibility Filters to their survey somewhere above the section that they would like to conditionally hide. Before doing this, they need to bring the Organisation Type into their survey by defaulting it into a question so it is accessible to both the survey and the filters. Typically, we don’t want the Organisation Type to be modified through the Survey, or even shown to the Survey Responders, so we would: 1) Create a question called 'Organisation Type' and default the information from the organisation module’s 'Type' field. 2) We would make the field 'Read Only' = Yes, and the field 'Visible = No' Once users have entered the information needed to configure a Visibility Filter, they can edit out a section, or create one if they don’t have one already. In this example, there is a Section called 'General Practice Organisations'. If a user only wanted this survey section visible when the organisation filling in the survey is a general practice, they should click the 'Add New Filter' link to create a filter and set the question field they are basing the test on to 'Organisation Type'. Then, set the operator to 'Is Equal'. Next, set the value to 'General Practice'. This will mean that if the organisation has a type of 'General Practice', this section of the survey will be visible. In other words, when the conditions of the Visibility Filter result in a TRUE test result, then the filter is active. If users have no filters, then the section of the survey is always visible. Using the operators, the conditionality tests can be mixed and matched to be fit for purpose. If additional filters are added, a choice can be made as to how each test relates to the other tests, with the ability to AND / OR the tests. Cross Validation Cross Validation allows users to add business rules to their survey to enforce conditions which are based on information in their survey. When the conditions fail their test, then a message, which users can specify, is displayed to the respondent. The choice can be made whether the validation rule is a warning raised for the respondent, which they then simply acknowledge before submitting their survey response; or if the condition prevents them from submitting their survey response until the issue is corrected. An example of where this would be used is if invoices were being collected for services delivered over a quarter, and the organisation providing the service must have current accreditation for them to submit their invoice. A check of the accreditation date, which would be held in ChilliDB, could determine if the invoice submission was accepted or not or, alternatively, force them to upload their new Accreditation certificate along with their invoice. This is achieved by adding Cross Validation Rules based on the Accreditation date, which would be a question with a default set to draw in information from the organisation record. This is exactly the same approach as the example of using the Organisation Type in Visibility Filters above. Once the Accreditation date is available in a survey, users can create a Cross Validation message and rules. First, click on 'Actions' from the drop-down menu while on the Survey Details page. Then, fill in the required fields on the 'Survey Cross Validation Maintenance' page. The fields are as follows: Purpose: is a simple description of the reason for cross validation. Message: which can be HTML formatted, is the message presented to the user when the conditions are not met. Cross Validation Message Location: the section of the survey where a message will be shown if conditions are not met. This flexibility allows users to prevent a respondent from leaving a part of the survey until they correct the issue. How this rule will be used: gives users the flexibility of having their cross validation present a warning for acknowledgment, allowing the survey respondent to accept the warning and continue without fixing it, or enforcing the rule conditions, meaning the respondent cannot progress any further without correcting the issue. Once this information has been entered, users click on 'Save' to save their cross validation. Now that the cross validation message and configuration have been created, users can specify one or more conditions. In this example, we will create a condition which checks our survey question regarding the Accreditation date and check that it is less than the closing date for our quarter. The result will be if the organisation is not accredited for the entirety of the quarter, then they will be asked to attach their new accreditation certificate along with their invoice. Once these conditions have been created, click 'Save' . Using the Operators, users can mix and match the conditionality tests to suit their purposes. If they add additional filters, they can then also choose how each condition relates to the other conditions they have created, with the ability to AND / OR each condition. They can have conditions which compare against constant values, or they could design complex surveys which check questions against questions.