## Forms 8 Documentation - Advanced Functionality

Quick Start | Field Types | Scripting | Server Data Options | Advanced Functionality

### Using Scripts to Perform Calculations

If you need to perform a calculation, you can add a script to the field in which you want to display the result of the calculation.

• The calculate: event is most commonly used in calculation scripts. A calculate event will run the script whenever any field on the form is updated.
• If you do not want the mobile user to be able to overwrite the result of a calculation, you can make the field which displays the result a read-only field.
• The answer statement assigns a value to the current field of the form. (Example 1)
For example, answer = \$1 + \$2 adds the values in fields 1 and 2 and places the result in the current field.
The \$N = expression statement assigns the value in the calculated expression to field number N. For example, \$5 = \$3 * \$4 multiplies the values in fields 3 and 4 and puts the result in field 5.
• Only binary math expressions are supported on any line of a script. This means that a math expression such as A + B + C takes two lines of a script. (Examples 2 and 3.)
• If a calculation involving a currency is performed, and the result is placed into a currency field, the result will display properly as a currency. If the result is placed in a Numeric or Text field, the number displayed will be in cents. A line can be added to the script to convert the cents to dollars and cents.
• If a form has a lot of fields, calculate: scripts may slow down performance since every calculate: script will run as each field on the form is filled in. To reduce the number of times a script has to run, you can use an exitscreen: event instead of a calculate: event. Exitscreen: events only run when the user exits the screen and moves to the next screen. Another possibility is to create a Button field and use a click: event script so that the mobile user controls when the calculation is performed, by tapping the button in the Button field.

Calculation Example 1: Performing a Simple Calculation
In the form shown below, the user can enter the price of an item and the quantity being purchased, and then calculate the total value of the items being purchased. The script to perform the calculation is in Field 4:

calculate:

A calculate: script is used in this case, so that every time the user updates the price or the quantity, the total value will be re-calculated as soon as the user leaves the updated field. The statement answer = \$2 * \$3 means that the answer to be placed in Field 4 is the multiplication of the value in Field 2 and the value in Field 3. On the mobile device, the calculate: script triggers when any field on the form changes. The user has to leave a field for the change in that field to be registered.

When the user fills in the Unit Price and Quantity, he/she will need to tap in another field for the calculation to occur.

Calculation Example 2: Adding more than two values together
The scripting language in Pendragon Forms only supports binary math functions, that is, math functions with two numeric expressions. In order to add more than two values, you can break a calculation into smaller parts, using the result variable as temporary extra storage space for storing intermediate results of a larger calculation.

In the form below, in order to calculate total meal expenses for the day in field 5, the statement result = \$2 + \$3 stores the sum of Breakfast (field 2) and Lunch (field 3) in the result variable. Calculation Example 3: Adding more than three values together
In this example, in order to calculate an average test score, the sum of test scores 1 through 5 must first be calculated. This is the script in Field 7 to calculate Total points:

calculate:
result = \$2 + \$3
result = result + \$4
result = result + \$5

The “# of Tests Taken” field records how many tests have been taken by adding 1 for each non-zero score:

calculate:

result = 0

if \$2<> null then
result = result + 1
endif

if \$3 <> null then
result = result + 1
endif

if \$4 <> null then
result = result + 1
endif

if \$5 <> null then
result = result + 1
endif

if \$6 <> null then
result = result + 1
endif

The script that calculates the average has a check to see if the number of tests taken (Field 8) is zero. If it is zero, the return statement ends the script to prevent a divide by zero error.

If Field 8 is not zero, then the average of Total points/# of tests is calculated.

calculate:
if \$8 = 0 then
return
else
endif

Calculation Example 4: Dividing
Whenever you perform division in a form, you have to be careful to avoid division by zero errors. These errors can occur because calculate: scripts are triggered whenever an entry has been made in a field. If you have a form in which a number X is entered, followed by a number Y, and you want to calculate X/Y, the value of Y will be zero until the mobile user enters a value. As soon as a value is entered for X, the calculate script will run, and X/0 will cause the letters NaN (Not a Number) to be displayed on the device. There are simple scripting statements which can be used to prevent the calculation from occurring until field Y has a non-zero value. Script to calculate A + B:

calculate:

Script to calculate A * B:

calculate:

Script to calculate A / B:

calculate:
if \$2 = null then
return
else
endif

Script to calculate (A+B)/(C+D):

calculate:
if \$8 = 0 then
return
else
endif

To calculate A / B in Field 7, a check is first done to see whether the divisor (number B in Field 2) is null (blank). If Field 2 is null, the return statement breaks out of the script so that the division is not performed. If Field 2 is not null, then the division of Field 1 by Field 2 proceeds.

Similarly, to calculate (A+B) / (C+D) in Field 9, a check is first carried out to see if the divisor (C+D) in Field 8 is zero.

Note: If you do not want to display too many decimal places, you can set the number of decimal places to display on the Data tab of each Numeric field in the Form Designer.

Calculation Example 5: Counter field
If you need to count the number of records in a form, there is a simple initialization script that can be used.

In addition to the script, it is necessary to make the counter field an Autodefault field on the Advanced Field Properties screen for that field. initialize:

Setting Field 1 to Autodefault means that when a new record is created, the value of the previous record is retained. The initialize script then adds 1 to increment the counter.

If you need to start the counter from 300, for example, simply enter the number 300 in the first record created. Subsequent records will be 301, 302, 303, etc.

Note that if the form is re-distributed to the device, or if the device is reset, the counter will be reset to 1.

### Working with Dates

Time fields, Date fields and Date & Time Fields can be used in calculations. Some notes:

• Dates are converted to numbers for calculations - the number of seconds since 01/01/1904.
• Results of calculations with dates must be stored in Text fields. It is not possible to subtract two times, for instance, and display the result in a Time field.
• The result of a calculation of two dates is expressed in seconds. The seconds can then be converted back to minutes, hours or days, as appropriate. See Example 1, below.
• An initialize: script can be used to set a default of the current date in a Date field, or the current date and time in a Date&Time field (see Example 1). Note however that the earliest date that you can set as a default is 01/01/1970.

Date Example 1: Today’s Date, and Time Elapsed
In this form, the first field defaults to today’s date, and other fields calculate the time elapsed between a starting and ending time. The initialize: script in Field 1 only runs once when the record is created. The answer = now statement places the current date (or date & time) into Field 1.

initialize:

calculate:

To calculate minutes, divide the seconds by 60.

calculate:
result = \$3 - \$2

To calculate hours, divide the seconds by 3600. (3600 seconds in one hour.)

calculate:
result = \$3 - \$2

Date Example 2: Displaying Time Elapsed in Hours and Minutes
Since most people are used to expressing time elapsed in hours and minutes, you may want to display the results of date calculations in this way. In Field 4, the time elapsed is calculated in seconds.

calculate:

The seconds are converted to hours by dividing by 3600, since there are 3600 seconds in an hour.
The integer statement takes just the whole number of hours, and this is placed in a field for storage.

calculate:
result = \$4 / 3600

The modulo (%) statement records a remainder, in this case the remainder of seconds after the whole number of hours is discarded.
The seconds are converted to minutes, and the whole number of minutes is stored in a field.

calculate:
result = \$4 % 3600
result = result / 60

To display the time elapsed as the phrase "X hrs and Y mins," the concatenate operator (&) is used to combine the whole number of hours, + the phrase "hrs and" + the whole number of minutes + the phrase "mins."

calculate:
result = \$7 & " hrs and "
result = result & \$8
answer = result & " mins"

Date Example 3: Calculating Ages
A useful calculation is to calculate a person’s age. The statement result = now - \$3 calcualtes the number of seconds from the date of birth to the present time and puts the answer in the result variable.
The result is divided by 86400 to convert seconds to days.
The number of days is divided by 365.25 to convert to years. (There are approximately 365.25 in a year, accounting for leap years.)

calculate:
result = now - \$3
result = result / 86400

The result can be truncated to two decimal places by multiplying by 100 to preserve two decimal places of precision, then adding 0.5 to round up.
The integer statement takes a whole number and discards the excess decimal places; diving by 100 reverts to the correct level of precision.

calculate:
result = \$4 * 100
result = result + 0.5
result = integer result

To round the present age to the age that the person will be this year, add 0.5 to round up, then the integer statement takes the whole number of years.

calculate:
result = \$4 + 0.5

### Branching

Scripts can be used in fields to allow branching on a form. With branching, the mobile user’s response in one field determines which additional fields are displayed.

• Put the extra (or optional) questions on a separate screen, and as the user exits the current screen, branch (jump) to that screen if needed, or jump past that screen if it is not needed.
The exitscreen: event is used to branch.
A select: event can also be used for branching if you want the user to jump to another part of the form immediately as a selection is made in a Popup List, Yes/No Checkbox or Lookup List field. However, a select: event will not run if the mobile user does not make a selection.
An exitscreen: event is therefore more failsafe than a select: event.
• The goto statement is used to branch from one field to another.
The goto statement can only be used in select:, exitscreen:, click: and scan: events.
• The hide and show statements are used to hide fields that the user does not need to fill in, and to display fields that the user does need to fill in. A field can be Hidden during the form design process in the Form Designer, and then the show or show from...to statements can be used to display fields as needed.
• Conditional statements, such as IF...THEN...ELSE...ENDIF and SWITCH/CASE are used to determine whether to branch to a question or not.

Branching Example 1: Branching from a Yes/No Checkbox field
In a Yes/No checkbox, there are three possible answers: Y for Yes, N for No, or null if the field is left blank. A branching script has to contain instructions for all possible answers. A blank response can be treated the same as answering No, if that is appropriate.

A select: event will run the script as the user makes a selection in the field. However, if the user leaves the field blank, a select: script will not run. An exitscreen: event runs when the user taps the Next button to move to the next screen, so an exitscreen: script will run even if the Yes/No field is left blank.

On the form below, Field 4 asks a Yes/No question. If the user answers Yes, then upon exiting the screen, the user will branch to field 5, which starts on the second screen of the form. If the user answers No, or leaves the Yes/No field blank, then he/she will skip all the questions on the second screen of the form, and will instead branch to field 9.

The exitscreen: event in field 4 runs when the user taps the Next button to move to the next screen. The if...then...else...endif statement sets up the branching conditions.

The statement means that if the answer in field 4 is Yes, the form will advance to display field 5:

goto 5 The else component of the if...then...else...endif statement covers what happens if the answer is not Yes, that is, if the answer is No or null.

else
goto 9
endif

This means that if the first condition (answer == Y) is not met, the form will branch to field 9.

On the device, selecting Yes in field 4 jumps the user to the next screen (field 5) when the Next button is tapped and the exitscreen: event runs.

Selecting No in field 4, or leaving field 4 blank causes the user to skip all the questions on the second screen, and jump ahead to field 9 on the third screen.

If the user jumps ahead to field 9, but then taps the Previous button, the screen with the skipped questions will be visible. Branching Example 2: Branching from a Popup or Lookup List
If you want to branch based on a selection in a Popup or Lookup List, your script must account for every possible selection that the user can make from the list.

A select: event can be used, but the user has to make a selection for the script to run. If the user leaves the field blank, the script will never run. You can use an exitscreen: event if you want the script to run when the user leaves the current screen, whether or not a selection has been made.

A switch/case statement is used to specify what branching will occur for each of the possible options in the Popup or Lookup List.

In the form shown below, field 10 is a Popup List with a list of travel destinations. Depending on the user's selection, a question relating to that destination will be displayed, and the form will advance to that question. The extra questions are hidden in advance by checking the Hidden checkbox on the Visual tab of the Form Designer window, and the script will unhide the relevant question. Here is the script in Field 10 in full:

exitscreen:
show 11
goto 11
case “United States”
show 12
goto 12
case “Europe”
show 13
goto 13
case “Asia”
show 14
goto 14
case “Africa”
show 15
goto 15
case anyvalue
endswitch

The exitscreen: event script has to contain instructions for each possible selection that the user can make in the Popup List.

exitscreen:

This means that the value in the answer variable (that is, the value selected in the current field, will be compared to each of the options in the case statements.

show 11
goto 11

This means that if the value in answer is Canada, field 11 will be displayed (show 11) and the form will branch to field 11 (goto 11). Similarly, each case statement details the actions that will be performed for each option in the Popup List.

At end of the script is this statement:

case anyvalue

Adding case anyvalue to the script will cover the actions to take if none of the case statement values match the value in the answer variable. For instance, if the user does make any selection from the list, the case anyvalue actions will be performed.

Adding case anyvalue to a switch/case statement is optional.

The last line of the script is:

endswitch

Every switch statement must end with the word endswitch.

Branching Example 3: Using a Goto statement with a Jump to Section field
A Jump to Section field contains some built-in branching capability that automatically allows you to jump to Section fields on your form. If you want the mobile user to branch back to the Jump to Section field after completing a section of a form, you can use a goto statement in the last field of that section.

In the following form, Field 7 is a Jump to Section field that allows the mobile user to jump to a section on the form. After the user has gone through the fields in a section, you may want the user to branch back to the Jump to Section field to be able to select another section.

When the mobile user exits the last field in a section, the form branches back to Field 7, the Jump to Section field. The Exit section is the only section which does not branch back to Field 7, so if the user selects the Exit option, he/she jumps to the final field(s) on the form and can end the record.

### Using Scripts in Button Fields

Scripts are used to carry out actions when the mobile user taps on a button in a Button field.

• The label on a button is set by typing in a Default value (up to 11 characters) on the Data tab of the Button field in the Form Designer window.
• The click: event is used to activate what happens when a button is tapped.
• The label on a button can be changed in a click: event script with the assignment statement answer = “Name-of-label”

Button Script Example 1: Calculate Button
Calculate: scripts run whenever a field is updated. This is processor intensive, and may also cause calculations to be performed before the mobile user is ready. An alternative is to use a button to give the mobile user control of when the calculation is performed. click:
\$9 = \$1 + \$2
result = \$3 + \$4
result = result + \$5
result = result + \$6
\$10 = result + \$7
\$11 = \$9 - \$10

In the form above, the last three fields on the form (Fields 9, 10 and 11) are not calculated until the user taps the Calculate button.

The advantage of using a button for calculations is that the user does not see intermediate results on screen before all the necessary data is input.

IMPORTANT: The disadvantage to using a button for calculations is that if the user changes a field, the calculated results do not change until the button is tapped again.

Button Script Example 2: Clone Button
In this example, the first few fields on a form will be the same for several records. To save the mobile user from re-entering the same data multiple times, a Button field is added to the form. Tapping the button clones the record, keeping the common data but erasing the fields that are different for each record. The user fills out the first record then clicks the Button field. The script in the Button field clones the first record, making a copy that keeps the value in the first two fields but nulls the value in the remaining fields on the form.

The script in the Button field of this form is:

click:
clone
\$3 = null
\$4 = null
\$5 = null The user can then fill out the remainder of the second record and click the Button field to create a third record.

The clone statement makes a new record that contains all the values from the previous record. The values in fields 1 and 2 (Date and Warehouse Location) are retained. The statements \$3 = null, \$4 = null and \$5 = null cause fields 3, 4 and 5 to be set to null (empty/blank) so that the mobile user can enter new values in the new record. At any time the mobile user can manually change fields 1 and 2 as well, and subsequently cloned records will contain these changes.

### Using a Script in a MultiSelection Field

MultiSelection fields are stored internally as a binary number, with each option in the MultiSelection List being represented by a bit position in the binary number. For example, the MultiSelection List shown here uses the following bit positions:
32: Yellow Cake
16: Lemon Cake
8: Chocolate Cake
4: Cherry Cake
2: Lemon Meringue Pie
1: Apple Pie

exitscreen:
if result = 1 then
\$7 = 200
else
\$7 = null
endif

if result = 2 then
\$8 = 250
else
\$8 = null
endif

if result = 4 then
\$9 = 300
else
\$9 = null
endif

if result = 8 then
\$10 = 250
else
\$10 = null
endif

if result = 16 then
\$11 = 250
else
\$11 = null
endif

if result = 32 then
\$12 = 250
else
\$12 = null
endif

Each checked box in the list sets the corresponding bit position to 1. Internally, the choice of Lemon Meringue Pie and Chocolate cake is stored as the binary number 001010.

For a script to react to the selections in a MultiSelection list, the binary AND operator can be used to check whether a given bit position has been set. In the script shown below, the answer in the MultiSelection field is compared to each bit position in turn. If the bit is set, the result of the AND operation is equal to the value of the bit position. If the bit is not set, the result is 0.

For example, the statement result = answer and 2 compares the answer in the MultiSelection field with the bit position 2, to test if the “Lemon Meringue Pie” checkbox has been checked. If it has been checked, a value of 250 calories is entered in Field 8, otherwise Field 8 is set to null. Field 8, which is on the next screen of the form, stores the calorie value of the Lemon Meringue Pie selection.

### Using Scripts with Parent forms and Subforms

A parent form and a subform are not really linked on the device - they only appear to be connected. Some scripts can be used to further enhance the appearance of a connection between the parent form and subform.

• The subformsum statement can be used to add up the values in a given field on a subform, and place the calculated result in the result variable. The value in the result variable can then be placed into a field on the parent form.

Adding across subform records, and placing the result on the parent form In the parent form shown here, Field 10 is a Subform field that jumps to a subform used to enter items being ordered.
Field 12 is a Button field on the parent form, that the users taps to run the following script:

click:
subformsum "Order - Subform" 8
\$13 = result
temp = \$11 / 100
\$14 = \$13 * temp
\$15 = \$13 + \$14

The statement subformsum “Order - Subform” 8 adds up the values in Field 8 of all the subform records that match the parent record. (In this example, Field 8 on the subform contains the total for one item being ordered.) “Order - Subform” is the name of the subform. The result of the calculation is placed in the result variable.

The statement \$13 = result then places the calculated result in Field 13 of the parent form. The remainder of the script calculates the tax and the total including tax.

Note that if the mobile user enters more subform records after the Calc button has been tapped, he/she will need to tap the button again to update the parent form with the new total.

Using Scripts to do a Cascading Lookup
A Cascading Lookup enables you to have a user make a selection in Popup List or Lookup List field, and then display a list of items relevant to their selection in the earlier field.

A Reference Form is needed to do a Cascading Lookup. Here is a sample Reference Form which will contain a list of rewards that a customer can earn. Field 1 is a Popup List for assigning a reward to a Gold, Silver or Bronze category. Field 2 of the Reference form is a Text field for storing the name of a customer reward. The Form Properties of the Reference Form have to be set to Keep Copy of Record on Device, and the default Additional Download Criteria of USERNAME = ##USERNAME## has to be erased to allow the records of the Reference Form to go to all devices.
Tip: To access the Form Properties screen, click the Properties icon next to the form name in the list of forms.

You can now create the form that will do the lookup to the Reference Form. One field on this form should be a Popup List or a Lookup List that allows the user to select a category. In this example the categories in Field 3 are Gold, Silver or Bronze. Another field on the form doing the lookup should be a Lookup List field, but instead of selecting a Lookup List to be displayed, select the name of the Reference Form. In this example the Reference Form is called Customer Rewards Ref1.

Important: The Field Name of the Lookup List should match the Field Name from the Reference Form that you want to copy data from.

After selecting the Reference Form to act as your Lookup List, click on the Script tab and enter the script that will make the lookup possible. In this example, the script is:

click:
select “Customer Rewards Ref1” where field 1 is \$3

The click: event script runs when the Lookup List field is tapped.

The select statement selects records from the Customer Rewards Ref1 form in which Field 1 of the Reference Form matches Field 3 of the current form. Field 3 of the current form is the reward category, so if the user selects a Gold reward in Field 3, when they tap in the Lookup List field they will see a list of Gold level rewards.

On the device, selecting an option in Field 3 determines which Lookup List will be displayed in field 6. Selecting Gold in Field 3... Displays all the records in the Reference form that have a Reward level of Gold.

Using Scripts to do a Double Cascading Lookup
A Double Cascading Lookup enables you to select records from a Reference Form based on two criteria instead of one as in a regular Cascading Lookup. For example, you might want to create a form in which you select a State, then select a City, and then see a list of customers in that City + State. Tapping in the City field brings up a list of Cities in the selected State. Tapping in the Company Name field displays a list of companies in the selected State and City. Selecting a company copies that company’s information into the form doing the lookup.

Three special fields and two Reference forms are required to do a Double Cascading Lookup.

One field is used to lookup a State. This field is just a regular Lookup List with a list of all the states.

The second field, City, does a single Cascading Lookup to look up the cities for the selected State. A Reference Form called “Cities and States” is used.

The third field, Company Name, does a Double Cascading Lookup to look up all the companies that match the two criteria of City and State. A Reference form called “Customer List” is used. The Reference Form needs a separate field for each criteria that you want to select.

This is the first Reference form, “Cities and States” that is used to look up a City once a State has been selected. Note that to copy fields into the form that is doing the lookup, the field names and field types have to match between the two forms. (A Text field can also copy into a Lookup List field.) In the Forms List, click the Properties icon next to the first reference form, in this case the “Cities and States” form. On the Form Properties screen check to Keep Copy of Records on Device. Also delete the default Additional Download Criteria of Username = ##USERNAME## to allow records to go to all devices. This is the second Reference form, called “Customer List”. The names of the fields on this form have to match the names of the fields on the form doing the lookup in order for data to copy from this reference form to the form doing the lookup. As with the first Reference form, the Form Properties of the “Customer List” Reference form have to be set to Keep Copy of Records on Device, and the default Additional Download Criteria of Username = ##USERNAME## has to be deleted to allow all records to go to all mobile devices. Now take a look at the form that is doing the Double Cascading Lookup. This form has the 3 fields needed to do the Double Cascading Lookup.

Field 1 is called State and is just a Lookup List field referencing a Lookup List called States with a list of states. Field 2 is called City, and is a Lookup List field that instead of referencing a Lookup List, references the first Reference form which is called States and Cities. Still in Field 2, on the Script tab is the script that selects all the cities that match the state from field 1.

The script is:

click:
select “States and Cities” where field 1 is \$1

This script selects all the records from the “States and Cities” form in which Field 1 of that form matches \$1 which is Field 1 (State) of the current form. Field 3 of the form doing the lookup is the field that does the Double Cascading Lookup. It is a Lookup List field that references the “Customer List” Reference Form. Next look at the Script tab of this field. This is the script that performs the Double Cascading Lookup:

click:
select “Customer List” where field 4 is \$1
click:
select “Customer List” where field 3 is \$2

The click: event runs when the user taps in the Company Name field to make a selection.

The first select statement selects records from the “Customer List” form in which Field 4 of “Customer List” (the State field) matches the State in \$1, Field 1 of the current form.

The also statement combines two select statements. The second select statement acts on the records already selected by the first select statement. The second select statement selects records from the “Customer List” form that, having matched on State, also match field 3 of “Customer List” (the City field) to \$2 – Field 2 of the current form, i.e. the City field. (847) 816-9660
info@pendragonforms.com
{"ft_lang_label":"__label__en","ft_lang_prob":0.8888372,"math_prob":0.91025573,"size":34522,"snap":"2023-40-2023-50","text_gpt3_token_len":7794,"char_repetition_ratio":0.17932673,"word_repetition_ratio":0.06945317,"special_character_ratio":0.22733329,"punctuation_ratio":0.08856893,"nsfw_num_words":0,"has_unicode_error":false,"math_prob_llama3":0.9570318,"pos_list":[0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"im_url_duplicate_count":[null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,4,null,null,null],"WARC_HEADER":"{\"WARC-Type\":\"response\",\"WARC-Date\":\"2023-10-05T01:33:15Z\",\"WARC-Record-ID\":\"<urn:uuid:a6df4c01-549d-459e-8610-7b220f729ef0>\",\"Content-Length\":\"107150\",\"Content-Type\":\"application/http; msgtype=response\",\"WARC-Warcinfo-ID\":\"<urn:uuid:01ef8c94-4a25-4699-9811-2c9a26af5f48>\",\"WARC-Concurrent-To\":\"<urn:uuid:ebc95c85-3551-47b4-b0c4-227f5c256fa8>\",\"WARC-IP-Address\":\"168.61.152.29\",\"WARC-Target-URI\":\"http://www.pendragonforms.com/documentation_advanced.html\",\"WARC-Payload-Digest\":\"sha1:6QMXGIKQBZJHG3KIPZQPUE32EJSIHADB\",\"WARC-Block-Digest\":\"sha1:KSY7JPUZAZSBHLWGRQ7MVFK26ZPTCF35\",\"WARC-Identified-Payload-Type\":\"text/html\",\"warc_filename\":\"/cc_download/warc_2023/CC-MAIN-2023-40/CC-MAIN-2023-40_segments_1695233511717.69_warc_CC-MAIN-20231005012006-20231005042006-00401.warc.gz\"}"}