The Count function is great, but many times, I need to count the number of things within a group (e.g., if there is a group of Kittens, I may need to count just the Kittens with green eyes). Here are the two scripts that do the same thing. If you are migrating to Advance from Developer, you may need to refactor your count computations to use a WHILE instruction rather than a REPEAT instruction. The HotDocs documentation still needs to be updated to reflect when the WHILE instruction vs. REPEAT instruction should be used for this purpose. Also, since the WHILE instruction will be necessary for some circumstances, it would be useful if the documentation for author could provide another example (https://help.hotdocs.com/preview/help/WHILE_Instruction.htm#:~:text=The%20WHILE%20instruction%20tells%20HotDocs,be%20used%20in%20the%20template.). Sample Scenario We need to count the number kittens with blue eyes. Repeat Instruction Script 0 REPEAT KittensDialog IF KittenEyeColor = "Blue" RESULT + 1 END IF END REPEAT WHILE Instruction Script - you need to create a local number variable. Here it is called "KittenCounter" SET KittenCounter TO 1 0 WHILE ANSWERED(KittenEyeColor[KittenCounter]) RESULT + 1 INCREMENT KittenCounter END WHILE

If they were recorded, are you able to share the recordings? I would definitely listen. I can also create a page on this website for video content like that. I think you have a good list. I have a HotDocs project I need to knock out next week. While I am working through my process, I will reflect on your list. I would be interest to know the limitations for the ASK function.

Hi Nicholas, These are great ideas! Let me share one idea that may seem a little complex but would help to move people from Developer to HD Author. Based upon my conversations with other developers, this topic causes concern for those who manage systems in production built on Developer, which relies on scripting to populate existing tables that act as answer sources (basically what the table variables are doing). These answer sources store critical information for the user (usually law firms or financial firms), which would be a severe issue if lost during the migration process. The video would address the following: (1) the migration issues and path for template libraries currently in production, which rely on populated multiple choice variables (using the index method) that are being populated from a table that is also being populated from a script that pulls in answers from a combination of repeated dialogs and normal dialogs. • Questions? If a template that utilizes this method (taught to me by HotDocs after the initial release of Author) is migrated in Author HD, can it continue to be used in Author? If not, how is this being handled since migration will result in a loss of data to the user? (2) Duplicate the system outlined in 1 above using table variables. Let me provide an illustration for a video that would be helpful: I have a multiple-choice question (WhoIsYourDaddyMC). (I am a reformed family law attorney, and this is the workflow I had to use in a case). Before the user got to this question, the user had to navigate through the following dialogs: (1) PriorBoyFriendList; (2) CurrentHusbandNormalDialog; (2) PriorHusbandList; (3) OtherList. Each list or normal dialog the user answered gathers the name and address of each potential father. Using a script, these lists and answers are merged into a MaybeYourDaddyList. Another script, WhoIsYourDaddyPopulateComputation populates the WhoIsYourDaddyMC but uses indexing. (a) Does this work in Author HD? (b) If not, how is this being resolved? If it has not been resolved, then the developers need to know about it because it seems like this would result in a loss of data for multiple-choice variables that rely on indexing. (c) What would this look like if I built the same setup using table variables?

I don’t know what the implications are. I have been really happy with the current staff and leadership at HotDocs. I received an email about the purchase this morning and it left me feeling anxious. Previous acquisitions resulted in years of confusion and constant employee turnover. Any assurances that there won’t be a slash and burn of the current HotDocs’ staff would be nice to hear.

@Nicholas Parenteau, can you provide some insights on this?

@Aaron Agnello Thanks for taking the time to make a video and post your solution.

I am familiar with this issue. Using the ERASE function does cause this Greying behavior when followed with a DEFAULT. While it is remedied if you navigate away and back to the dialog, this is no a good solution. Is there a reason that you cannot use the SET function instead? IF partyPopulatePartyWithOwner = "owner1" //Erase incase the owner has changed their mind (selected owner2, and now selects owner1) SET partyFirstName TO own1FirstName SET partyMiddleName TO own1MiddleName SET partyLastName TO own1LastName ELSE IF partyPopulatePartyWithOwner = "owner2" //Erase incase the owner has changed their mind (selected owner1, and now selects owner2) SET partyFirstName TO own2FirstName SET partyMiddleName TO own2MiddleName SET partyLastName TO own2LastName END IF

You cannot place a computation that references dialogPartyNamePart1 (a repeated series) within dialogPartyNamePart2 (a repeated series). IF Both repeated series have the same variables then you you could try using the HIDE ALL instruction. At the end of the Dialog Script, add in your version of the following. IF doesPartyLikeGreen = TRUE HIDE ALL END IF This will hide the instances of a repeated series that meet that condition while showing the remaining.

The "linking Variables to a Dialog" selection is found on the options page when you are working within a dialog. See the image below. If you unselect this option, this will allow you to place the same variable within two different dialogs. This will allow you to place the As Confirmed by US variable into two different dialogs. For your situation, if a new party is added to the Party Name dialog then this will automatically create another instance of the repeated dialog that will later show the As Confirmed by US variable when applicable. You can also add a script to only show iterations of a dialog that have the correct conditions. The instructions that I provided do the following. 1. The As Confirmed by US variable is included within the Party Dialog (repeated dialog) and another repeated Dialog, lets call it OtherDialog. 2. When you add a party, this will also add an new iterations of the OtherDialog. 3. Within the "OtherDialog" you can add a script that show or hide an entire dialog based upon specific conditions. My solution, outlined in my other response would take about 10 minutes to build a test case for.

Hi @SamanthaJane, I am glad to provide a resource for everyone. If you know any other developers, please let them know that they can post here. The only way this becomes useful is if people know about it. Please feel free to share ideas on what might be useful on this site. I just added a new category directed towards the experience of migrating from Developer to HotDocs Advance/Author.

This can be a little buggy, but I have used this in the past. I am sure that using a loop to create a new dialog is also available. I suspect that @bart will have a better approach. 1. Put the "As Confirmed by US" variable within the "PartyName" dialog. 2. HIDE the "As Confirmed by US" variable within the "PartyName" dialog 3. Default "As Confirmed by US" this variable to "No" 4. Create the new repeated dialog, we will call it "AsConfirmedByUsDE". Be sure to uncheck the "Link variables to this dialog" on this dialog and the "PartyName" Dialog. 5. Put the "As Confirmed by US" variable within the "AsConfirmedByUsDE" 6.  Put all the other variables that would control when the "AsConfirmedByUsDE" would show or hide within the "AsConfirmedByUsDE" 7. Within the Script section of the "AsConfirmedByUsDE", I would try the following script. HIDE ALL IF (Your Condition that would show the "As Confirmed by US" variable) SHOW As Confirmed by US REQUIRE As Confirmed by US HIDE ALL END IF LIMIT (insert a Number Variable that represents the number of iterations of PartyName) 8. I added a LIMIT instruction at the end because this will disable the "Add Another" button at the bottom of the page. You would have to create and set the Number Variable in the custom interview component or in another dialog. I am sure this could also be done by using loops, but the solution would be more involved. I am unsure how elegant your solution needs to be.