After you have designed a wizard, you must thoroughly test it and resolve any problems that may arise.
The following table lists common problems and possible solutions to them.
Wizard Troubleshooting Tips
Possible Problems |
Possible Solutions |
|
The New button does not appear at all on the TeamConnect user interface. |
The Require wizard for new object definition check-box is selected, but there are no active wizards. Either clear this check-box or activate a wizard. Note: This does not apply to Contacts—a New button is always visible because it is also used to create Address Books. |
|
The wizard is not displayed in the New drop-down list. |
Make sure the wizard is activated by selecting the This wizard is active check-box on the General tab of the wizard. |
|
I want users to only be able to create records by using a wizard, but when I click the New drop-down list, I still see the wizard option and the blank record option. |
Select the Require wizard for new object definition check-box on the General tab for the wizard. See the General Tab on Wizard Screens table for more information. |
|
The selected wizard cannot be started. |
•Make sure the correct automated action file is selected as the initial action for the wizard. •Ask a developer to check the code in the initial action file. |
|
The wizard never ends. |
Make sure the page transition rules are added properly, and no loops are created by switching the same pages over and over again. |
|
Page order is not correct. |
Pages do not follow each other in the order that was assigned to them on the Pages tab. |
Make sure there are no page transition rules added to your wizard pages on the Page Transitions tab, because this action modifies your default order. |
Make sure there are no Final pages added in the middle of your default page order. |
||
Certain pages never display. |
Make sure they have not been accidentally deleted from the wizard. |
|
Make sure the page transition rules are added correctly. All possible options for the user input are accounted for. No loops are created. |
||
Make sure there are no final pages added in the middle of your default page order. |
||
Make sure no pages with the added page transition rules have been deleted, thus breaking the sequence. |
||
Pages are not skipped as appropriate or appear when they are supposed to be skipped. |
Make sure the qualifiers are set correctly in your page transition rules. All possible options for the user input are accounted for. |
|
Transition rules use the wrong values. |
Make sure the parameter and custom field names in custom blocks are unique. |
|
The wizard goes to the final page without having gathered all the necessary information. |
Make sure you use the appropriate user account to test your wizard. For example, if you are an Administrator, and the wizard is set to allow creating records only to the users with the role Claim Associate or Claim Adjuster, you are not able to proceed. |
|
Make sure the required fields are populated. |
||
Records are not created. |
The wizard does not allow you to save the record when clicking Finish. |
Required fields may not have been populated or were not added to the wizard. For example, a parent record, or a custom field that are included in the object views. |
The wizard exited but the record was not created. |
Make sure the Create the record on finish check-box is selected on the Page Transitions tab of the Final pages appropriately. |
|
The wizard was supposed to end without creating the record, but the record was created. |
||
No related records were created when the wizard finished. |
Make sure the appropriate template is linked to the wizard in its General tab. |
|
Make sure the appropriate related objects are added to the template linked to the wizard. |
||
The assigned default values are not populated correctly in the saved record. |
Make sure the correct attributes or paths were selected for the fields in the template or on the Actions tab of the wizard. |
|
Make sure the values assigned in the template are not overwritten on the Actions tab of the wizard, by the initial action, or manually when working with the wizard. |
||
Layout and Formatting |
The fields and their labels are not aligned. |
Consider putting individual fields into a separate custom block. |
The fields and their values are not formatted appropriately, for example, to display time, dollar amounts, and so on. |
Create custom blocks for the custom fields and add the appropriate formatting tag attributes. Tip: You may add basic HTML formatting to the text components, such as bold, italics, underline. |
|
The last page in the wizard does not have the finish button. |
Make sure it is set as a final page on the Page Transitions tab. |
|
Duplicate parameter fields appear on the same page. |
If you have included parameters in a custom block, make sure the Display in blocks only check-box (see the Select a Wizard Pop-up Window image) is selected on the page where the parameter is defined. |
|
Parameters do not appear on the page. |
If the parameters are not included in custom blocks, make sure the Display in blocks only check-box (see the Select a Wizard Pop-up Window image) is not selected. If the parameters are included in custom blocks: •Make sure the block is added to the page where the parameters are defined or on any other page that follows. •Check whether the parameters are within a <tc:section> tag that contains custom fields in the custom block. If they are, either make sure the category to which the custom fields belong is added to the record that is being created through the wizard, or move the parameters outside a <tc:section> tag (see Sample XML File). |
|
Custom Blocks |
Blocks take long to load. |
The first time you are using your wizard, it may take a little longer to load the custom blocks, because they need to be cached locally. |
Block does not appear on the wizard page. There is an error instead. |
The XML file may have problems. Make sure the custom block was created properly. For details, see: |
|
Miscellaneous error messages may appear during the testing phase. |
Make sure the fields used in actions or page transition rules are populated. |