Specific instruction for FormSlab and DoubleWall for the IMPACT 17.3 version

Last modified by Peter Karlsson on 2026/08/27 08:44

This article describes how FormSlab and DoubleWall behave in IMPACT 17.2, and what changed in IMPACT 17.3 specifically regarding saving/storing of elements. 
It also describe the process for a project in 17.2 moving to 17.3 (after the migration).

IMPACT 17.2 behaviour

FormSlab

Elements are first marked then saved when generating shop drawing or as a separate save to database.

FormSlab172.gif

All components are added to the element when shop drawing is generated.

When changes are made on floor plan no indication is showing that the element is not saved.

DoubleWall

Elements are first marked then saved when generating shop drawing or as a separate save to database.

DoubleWall172.gif

All components are added to the element when shop drawing is generated.

When changes are made on floor plan no indication is showing that the element is not saved.

What changed in IMPACT 17.3

FormSlab

Elements that are matching can get the same element mark if the setting is changed in Project Properties (Default is as before Never – always use new mark).
1774862477462-511.png

Components need to be added to the element (if not directly added when drawn) with add (just like for all other element types).
FormSlab173.gif

When changing an element that is saved it will be indicated with the * after the element and change in color so that missing to save after the change will be avoided. 

DoubleWall

Elements that are matching can get the same element mark if the setting is changed in Project Properties (Default is as before Never – always use new mark).

1774870782935-149.png

Components need to be added to the element (if not directly added when drawn) with add (just like for all other element types).

DoubleWall173.gif

When changing an element that is saved it will be indicated with the * after the element and change in color so that missing to save after the change will be avoided.

Existing elements when moving from 17.2 to 17.3

FormSlab

When update plan is run for the first time on an existing floor plan (created before the migration to 17.3):

  • The unsaved elements that only have been marked will be unmarked.
  • The elements that have been saved (and shop drawing generated) will get a star star after the element mark.
  • The elements that have an pending update will be listed in the command window.

FormSlab172 to 173.gif
If you have a pending update plan that change coming from changes on the shop drawing can’t be performed so instead you need to remove the element (answer no to remove from database) and then generate it in again if you like to get the change from the shop drawing into your floor plan. If you have done changes on the Floor plan on that element that is not changed you can also decide to use that instead and then you can save the element on the floor plan and then generate the shop drawinng again from the floor plan.

DoubleWall

When update plan is run for the first time on an existing floor plan (created before the migration to 17.3):

  • The unsaved elements that only have been marked will be unmarked.
  • The elements that have been generated a shop drawing will get a star star after the element mark.
  • The elements that have an pending update will be listed in the command window.

DoubleWall172 to 173.gif

If you have a pending update plan that change coming from changes on the shop drawing can’t be performed so instead you need to remove the element (answer no to remove from database) and then generate it in again if you like to get the change from the shop drawing into your floor plan. If you have done changes on the Floor plan on that element that is not changed you can also decide to use that instead and then you can save the element on the floor plan and then generate the shop drawinng again from the floor plan.

Recommendations before upgrading to IMPACT 17.3

Make sure that your floor plans are updated before migrating to 17.3.