Move variables, templates and events from one database to another

Modified on Thu, 14 Mar at 1:43 AM

To move variables, templates and events from one database to another you need to use the Dump and Load feature. 


Be careful: Although you are prompted about overwriting existing items, loading items into a database will overwrite existing items and can not be undone. ALWAYS make and keep a copy of items in the system you are writing to before you do the update. New items will be added without further warning and these will not be removed by reloading from a dump file backup.


Step-by-step guide


Backup the variables, templates and events in the database you are copying to: 


For Variables:

  1. Go to the database you want to copy the variables to. 
  2. Go to Main Menu > Workflow Development > Template Variables. 
  3. Choose the Template you want to dump the variables from e.g. ZZZZ.


  4. Select the variables you want to dump out using your CTRL or SHIFT keys. 
  5. Right click the selected variables and choose dump. 
  6. Choose the Selected Rows option.


  7. Click OK. 
  8. Set the location and name of the xml dump file to somewhere you will be able to find it later. 
  9. Click Save. 
  10. Repeat steps 3 to 9 for each Template you want to dump the variables from. 
  11. Keep the resulting xml file safe as a backup just in case!


For events:

  1. Go to the database you want to copy the events to 
  2. Go to Main Menu > Workflow Development > Task Management 
  3. Choose the Template you want to dump the variables from eg) ZZZZ


  4. Select the events from the Events column you want to dump out using your CTRL or SHIFT keys 
  5. Right click the selected events and choose dump 
  6. Click No


  7. Set the location and name of the xml dump file to somewhere you will be able to find it later. 
  8. Click Save 
  9. Repeat steps 3 to 9 for each Template you want to dump the events from 
  10. Keep the resulting xml file safe as a backup just in case!


For Templates: 

  1. Go to the database you want to copy the templates to 
  2. Go to Main Menu > Workflow Development > Document Templates 
  3. Select the templates you want to dump out using your CTRL or SHIFT keys 
  4. Right click the selected templates and choose dump 
  5. Choose the Selected Rows option and make sure the “Include Documents” tick box is ticked


  6. Click OK 
  7. Set the location and name of the zip dump file to somewhere you will be able to find it later. 
  8. Click Save 
  9. Keep the resulting zip file safe as a backup just in case! 


Copy the variables, templates and events from one database to another


For Variables:


DUMP

  1. Go to the database you want to copy the variables from 
  2. Go to Main Menu > Workflow Development > Template Variables 
  3. Choose the Template you want to dump the variables from eg) ZZZZ


  4. Select the variables you want to dump out using your CTRL or SHIFT keys 
  5. Right click the selected variables and choose dump 
  6. Choose the Selected Rows option

     
  7. Click OK 
  8. Set the location and name of the xml dump file to somewhere you will be able to find it later. 
  9. Click Save 
  10. Repeat steps 3 to 9 for each Template you want to dump the variables from


LOAD

  1. Go to the database you want to load the variables to 
  2. Go to Main Menu > Workflow Development > Template Variables 
  3. Choose the Template you want to load the variables to eg) ZZZZ


  4. Check the list of variables you are planning on exporting with the list of variables in the new database and make sure you are not going to overwrite any variables you don’t intend to 
  5. Right click in the grid and choose Load 
  6. Select the XML file you saved in 9) above 
  7. Click Open
  8. The variables will now be loaded to the new database overwriting any and all variables named the same as those being loaded. 
  9. Repeat steps 3 to 9 for each Template you want to load the variables from


For Events:


DUMP 

  1. Go to the database you want to copy the events from 
  2. Go to Main Menu > Workflow Development > Task Management 
  3. Choose the Template you want to dump the variables from eg) ZZZZ


  4. Select the events from the Events column you want to dump out using your CTRL or SHIFT keys 
  5. Right click the selected events and choose dump 
  6. Click No


  7. Set the location and name of the xml dump file to somewhere you will be able to find it later. 
  8. Click Save 
  9. Repeat steps 3 to 9 for each Template you want to dump the events from


For Templates:


DUMP 

  1. Go to the database you want to copy the templates from 
  2. Go to Main Menu > Workflow Development > Document Templates 
  3. Select the templates you want to dump out using your CTRL or SHIFT keys 
  4. Right click the selected templates and choose dump
  5. Choose the Selected Rows option and make sure the “Include Documents” tick box is ticked


  6. Click OK 
  7. Set the location and name of the zip dump file to somewhere you will be able to find it later. 
  8. Click Save


LOAD

  1. Go to the database you want to load the templates to 
  2. Go to Main Menu > Workflow Development > Document Templates 
  3. Check the list of templates you are planning on exporting with the list of templates in the new database and make sure you are not going to overwrite any templates you don’t intend to 
  4. Right click in the grid and choose Load 
  5. Select the ZIP file you saved in 8) above 
  6. Click Open 
  7. The Templates will now be loaded to the new database overwriting any and all Templates named the same as those being loaded


NOTE: If you added any new parameters to your old database make sure they get added to your new database too. This might be things like matter parties, work types, templates etc.

WARNING: The parameter copy process, though similar to the above WILL NOT WARN YOU WHEN OVERWRITING. Exercise care when updating parameters, as incorrect updates can significantly impact the operation of your system.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article