https://community.appian.com/discussions/f/process/11952/disappearing-security-settings-in-version-17-2-gWe are currently on version 17.2 of Appian however, there are still some old process models in version 16.2 E that were not converted to SAIL. They still require updates and maintenance. Until they are converted to SAIL models, I am facing an issue thaten-USTelligent Community 12https://community.appian.com/thread/52870?ContentTypeID=1Thu, 22 Feb 2018 14:59:31 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:aadb2c65-3cfc-4474-b45b-0f1a86ac5250tonycThe conversion to SAIL is definitely a priority and we have been working diligently towards that goal. All new work is being coded in SAIL. We have a bit of old legacy models and are catching up with SAIL in a very positive manner and hard teamwork. As of now, I have observed this behavior on the old legacy models. You might be in the right ballpark with your response.<div style="clear:both;"></div>https://community.appian.com/thread/52867?ContentTypeID=1Thu, 22 Feb 2018 14:43:55 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:86ebcbad-3ce4-4a83-b087-8133314550efAshvin KapurTony,<br /> I haven&#39;t experienced that issue before, but I just wanted to clarify - you mean there are process models in which the forms / user input tasks have not been converted to SAIL forms? Process models are configured in similar ways pre- and post- SAIL. How many models is this happening for? Do you have any models where some forms are coded in SAIL and others using the legacy forms designer?<div style="clear:both;"></div>