Using data from completed documents

With Incontrol, it's possible to import data from previously completed documents. By using the 'Import document' element in your forms, you can specify which documents from a specific form you want to import. This saves time for the user when filling out a draft.

Table of contents

1. Setting aliases for imported documents:
2. Adding an import element
3. Importing data
4. Whitelisting and alias mapping
5. Importing dynamic elements
6. Using blacklisting
7. Making import mandatory
   
   

Setting aliases for imported documents:

• Use aliases in your form that exactly match the aliases in the source form.
• Before you can continue working with the data, you must activate the alias in the top right corner of the element, both in the source form and in the form you are importing into.
• Once an alias has been activated once, you can reuse it anywhere. For example: once you have activated @municipality (as shown in the example below), you do not need to do this again for a subsequent element.
  
  

Remember that this must be done again for each alias that you want. 

• This for dynamic elements: note down all aliases within the element, not just the dynamic alias itself.
• For images: set the input method to user input.

Add import element 

• Add the Import document element from the “Import” section.
• Select the form from which you want to import data.
• All documents from the selected form will become available, including those from other users or security groups.

Element settings

• Label: give a title, which can be filled in using aliases or calculations.
• Text: editable text, which can be filled in using aliases or calculations.
• Form: select the source form.
• Button text: text on the import button, which can be filled in using aliases or calculations.
• Design: change the appearance of the element.

Import data 

• Click on the import button while filling in the form.
• Search by document name and select the correct document; the data will be filled in automatically.

Whitelisting and alias mapping 

Whitelisting

• Import all aliases: all matching aliases are included.
• Import specific aliases: enter the aliases you want to import, each on a separate line.

Alias mapping (elements)

• Link source aliases to form aliases: @alias >> @new_alias
• Multiple aliases can be linked using enter keys.
• One alias can be linked to multiple form aliases.

Alias mapping (dynamic elements)

• Dynamic elements: @dynamicalias >> @new_dynamicalias
• For aliases within dynamic elements: @dynamicalias @alias >> @new_alias
  
  

Importing dynamic elements 

• First link the dynamic alias to the new dynamic alias.
• Then link the aliases within the dynamic element to the new aliases.
  
  

Using blacklisting 

• To prevent certain aliases from being imported: give them a new alias that does not exist in the form.
• For example: @import_alias >> @doesnt_exist
  
  

Making import mandatory

• Use the element settings to specify that a user must always import something before the form can be completed.