Features

We sometimes need to advertise information about customer-facing automations to form users. For example, if there's a known issue on the Rewst platform or we just want to send some automation-related information out to form users. We'd like the ability to add a banner object to a form, and that banner display the information. The information would be defined at the top level organisation, or perhaps also have a customer level banner too.

We need the ability to embed/provide forms publicly. We have a lot of forms that are used by outside vendors and/or new clients that are not yet in AAD. For example, we have a Site Survey form that 1099 field techs complete. Another example, a new client that is in the process of onboarding may not have AAD as part of our onboarding is to migrate them from hosted Exchange/etc. We still need to provide them with forms for: Company Details, Billing Details, Sites/Locations, Employee Listings, Letters of Agency and many more.

Similar to what exists for Workflows, the ability to view the change history for forms and roll back to a previous version of the form.

Currently, when a default value (true) is specified in the options list, the form correctly preselects the corresponding value. However, if the next options list does not contain any true value, the previously preselected item is not cleared, as no new default is detected. This behavior can lead to incorrect or outdated selections persisting in the field. Requested Enhancement: Introduce a feature where, if all options in a dropdown list have their default value set to false, the preselected item is automatically reset. This ensures that the dropdown accurately reflects the updated options and avoids retaining outdated selections. This functionality would improve form usability and accuracy, especially when switching between dynamic or conditional option lists. Example: 1st Options Context: options:[ { default:true id:"xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx" label:"group1" } { default:false id:"xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx" label:"group2" } ] Result: Preselects group1 (expected). 2nd Options Context: options:[ { default:false id:"xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx" label:"group1" } { default:false id:"xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx" label:"group2" } ] Current Behavior: Dropdown still preselects group1 (previous value/incorrect). Expected Behavior: In the 2nd options context, the dropdown should reset to null (no selection) when no option has default: true.

Forms that can be split into multiple pages so related fields can be seen on one page, and also certain pages to be displayed/hidden based on the selection in some other fields.

The ability to split a form in to multiple columns, so that it doesnt end up so long. I am developing an App with a form which has several inputs on it. Filling out the form can involve a fair amount of scrolling up and down. Multiple columns could allow all the questions to appear on the same screen at once. Much better customer journey :)

We have some cases where a form option needs to give guidance on something rather than result in a form submission. Could the ability to add Jinja/logic to the Submit button like any other form element be implemented please?

Currently, you are only able to add one jinja condition to form elements. Would like the ability to have multiple jinja conditions so you can do things like require a field and show it based on a jinja evaluation. Current Implementation Add element to form. Add jinja condition to element. Repeat step 2. Still only have 1 jinja condition. Suggested Implementation Add element to form. Add jinja condition to element. Repeat step 2. Now have multiple jinja conditions applied to the form element. Acceptance Criteria Ability to have multiple jinja conditions applied to a form element. has context menu Compose

As a service desk manager I'd like to be able to see a report (or widget) on utilization per Form. This would allow me to measure the usage of Forms in Rewst to understand utilization and investigate opportunities to improve Forms and automation.

I have some unsync'd custom copies of forms from unpacked rewst crates. Id love the ability to either hide the original or limit access to forms in general within rewst to prevent my team from accidentally selecting the original form instead of the updated one.