Typically, once a slab is tagged to a job and then fabricated, the slab's status will change from "Available" to "Used" after the "Use" button is clicked in the Fabrication tab.
And then, after the job/area is installed, the slabs all have an "installed" status.
![InstalledStatus](https://support.actionflow.net/hs-fs/hubfs/Knowledge%20Base%20Articles/SlabStatus/InstalledStatus.png?width=688&height=295&name=InstalledStatus.png)
However, there are some cases where the area status may change to "Installed" before the slab's status is changed. This means, the slabs were never marked as "Used" before the job/area was installed.
If there is an "Available" slab on an area when the job/area status changes to "Installed," what happens to the slab?
There are 2 scenarios for how your shop could handle any "Available" slabs.
Scenario 1 (default setting) assumes that once slabs are tagged to a job, they are always used for that job.
- Any tagged slabs on the job get set to "installed" automatically when the area status is set to "installed"
Scenario 2 assumes slabs that get tagged to a job may NOT always be used for that job and in that case, you want to make them available on other jobs. This requires that someone at your shop will manually confirm whether slabs were used.
2. Only slabs with a "used" status get set to "installed" automatically-
- ActionFlow indicates to the user that there are slab(s) tagged to the job that have an "available" status
- The user should confirm whether the slabs were used as part of that job or not
- if the slabs were NOT used, the user should untag the slabs so that they are available for other jobs
- if the slabs WERE used, the user could click the "use" button in the fabrication tab
- Because the area has already been changed to an "installed" status, the new status for the slab(s) will jump straight to "installed" instead of "used"
- Because the area has already been changed to an "installed" status, the new status for the slab(s) will jump straight to "installed" instead of "used"
- if the slabs were NOT used, the user should untag the slabs so that they are available for other jobs
- If the user does not update the "Available" slab after install, ActionFlow will automatically untag the slab after 7 days.
- ActionFlow indicates to the user that there are slab(s) tagged to the job that have an "available" status
By default, ActionFlow will follow scenario 1 and assume all tagged slabs on a job should get set to "installed" if the job/area status changes to "installed."
If you would like to enable scenario 2, talk to your account manager.
Administrators: Uncheck the "Set Slab to Installed with Area" box in the master settings to enable the 2nd scenario.