Release
How can I get the new form builder?
The new form builder was released in Continuum XFP #75 on the 13th March 2018 as part of the fortnightly release package issued by the XFP team. In order to use the new form builder you will need to request a patch of your site via Jadu Support for this version or above on or after 13th March 2018.
If Jadu/Creative deploy patches for you, the patch will be scheduled in with the deployment team via the usual deployment process. If you patch yourself, a package will be provided to you.
Once Continuum XFP #75 or above has been deployed to your site, Jadu will need to update your sites configuration to enable the new form builder before it becomes available to use (is disabled for existing customers by default).
When can I get it from / what release number?
The new form builder was released in Continuum XFP #75 (semantic version 4.0.0).
What are the system requirements for the new form builder?
There are no new system requirements introduced for the new form builder, your existing infrastructure and configurations (assuming that you have XFP already installed) should be sufficient. Some installations of PHP do not have the FileInfo module installed, you can check if you have this module installed or not by logging into your control centre and changing the url to jadu/maintenance/phpinfo.php and searching for FileInfo. If you do not have this PHP module installed you will need to install it.
We do however recommend that you install OPcache if it’s not already installed.
I have the latest patch but I can’t see the new form builder, why not?
The new form builder is not enabled by default, Jadu will need to enable the new form builder in your site configuration before it is accessible. This is to allow a phased approach for roll out across all of Jadu’s XFP customers. If you would like to have the new form builder enabled please let us know via Jadu Support where we will advise on the steps required to enable the new form builder for you and any costs associated.
Will I / Creative need to implement new templates for me?
You won’t need a full re-implementation of templates, but the new form builder templates will need to be developed and implemented which can be done through our professional services team.
Will forms built in the new form builder look the same as they do now?
Forms built in the new form builder will use Jadu’s Photon templating engine, so they will look broadly similar, but you can expect some minor differences, as all implementations have historically been handcrafted, so it’s important that you test your implementation once updated to check that you understand how things now display and behave.
Can we implement it just in UAT first to have a play / test / train?
Yes absolutely, the new form builder is disabled by default and can be turned on in UAT and remain off in production until you are ready to use it on your production site.
Can I implement the new form builder upon our local environment myself?
Yes, if you would like to do this then just get in contact with us and we can discuss how you would go about doing this.
Are there different templates for each of the form builder interfaces?
Yes, the legacy form templates have not been changed for the new form builder. The new form builder uses the Jadu Photon templating engine to render the form user interface.
Training
Will you be providing training?
Jadu recommend face to face training to go over the new features in form builder, this can be arranged at £1000 per day plus VAT and expenses (maximum 8 delegates per day).
The user manual has also been updated and is available online at https://www.jadu.net/support/manuals/xfp/ and provides a good source of information on the new form builder.
What supporting materials will be provided?
The user manual has been updated and covers all of the new features. We’ll also be providing training videos that cover all the functionality of the new form builder.
Will the way we approach custom developments internally need to change?
Yes, we’ve tried to make developing custom form components and actions easier for developers. There is now a new framework for plugging into the new form builder. The rules engine and components are no longer based within the database, giving you more flexibility and making these easily shareable.
Developer documentation is available on request.
Are there new developer extensions that I can do in the new that I couldn’t do in the old?
Yes, it’s now possible to build your own form components. In the legacy form builder, developers could build custom Integrated Components but the markup generated by these components wasn’t customisable and relied on the from builder to join the elements together. Now in the new form builder, developers can design their own components controlling all aspects of the component down to the HTML markup that is used to display the component.
It’s also now possible to add your own form variables to the standard set as a new extension capability.
Existing customers
Is there any cost for the new form builder?
There is no cost for the new form builder, as part of Continuum XFP you will get the new form builder when you update your site to our latest release version as part of your existing support contract.
There will be a professional services cost to provide additional styling specific to your templates for the new form elements that do not exist in the legacy form builder.
There may also be a separate cost in changing any existing custom developments that you may have to be suitable for the new form builder. The cost for updating the custom developments will need to be quoted on a case by case basis.
Can I opt out of the new form builder?
No it is not possible to opt out of the new form builder.
Jadu will only be supporting the legacy form builder until at least the end of 2020. No new features, apart from those required for GDPR compliance, will be developed for the legacy form builder and only security issues will be fixed in the legacy form builder after March 2018.
We hope that you will want to use the new form builder, if you have any concerns please speak to us about those.
When do I have to migrate my old forms by?
The legacy form builder will remain supported within XFP until at least the 31st December 2020. You should have all your forms that are in the legacy form builder migrated into the new form builder before that date.
Jadu have updated the reporting tools in XFP to provide a report for how many forms you have and in which version of the form builder they exists so as to help you plan the migration of your forms.
Will the old ‘Classic’ forms continue to function?
Existing forms will continue to function until XFP 11.0.0 is released and patched to your environment. XFP 11.0.0 is expected Spring 2022 will be the version from which the classic form builder and classic forms will be removed from the product. Until we ship XFP 11.0.0, we will continue to review and consider issues raised concerning the classic form builder through the interim period, on a case-by-case basis. We are likely to limit the resolution of issues to P1 and P2 issues
What help will Jadu provide to migrate my old forms?
Jadu will not be providing a migration tool to assist in migration of forms.
Due to the differences between legacy forms and new forms to perform a complete like for like migration. For example the Table component in the legacy form builder has been replaced by the Matrix page element and repeatable question types in the new form builder and you may wish to review how these differ in your own form designs.
Jadu will be on hand to offer advice for migrating your forms and using the new features to streamline your existing forms.
Can I use my old forms and new forms simultaneously?
Yes, the new form builder is installed alongside the legacy form builder and uses a separate code base and front end scripts. Your old forms will continue to function as they have before the new form builder release.
I have existing custom developments will they still work?
The nature of the custom developments mean it’s hard to be certain but we’ve tried to keep as much backward compatibility as possible.
- Integrated Components: All custom Integrated components will be available in the new form builder under the ‘Integrated’ page element.
- Form actions: Form actions will need to be updated to support the new form builder template and rules engine. Advice for developers will be provided for updating custom actions to support the new form builder.
- Predefined calculations: Custom predefined calculations will be available under the Logic tab within the new forms builder.
- Front end scripts: Any front end changes that you have applied will not be compatible with the new form builder. The new form builder uses Photon templating, to re-apply any front end script changes you will need to extend the templates.
Advice on how to do that can be provided on request.
How long will you support the old form builder for?
The legacy form builder will remain usable within core XFP until at least 31st December 2020, after which it will be removed from the core product.
From April 2018 no new features, apart from those required for GDPR compliance, will be developed for the legacy form builder and only security issues will be fixed.
I have outstanding support tickets relating to the old form builder, will they be fixed?
We do not anticipate resolving any further issues apart from those that relate to the security or integrity of your data. If your issue is a security issue then this will be prioritised and fixed as per any other security issue. No new features (apart from those required for GDPR compliance) will be developed for the legacy form builder after March 2018.
If your issue is not reproducible in the new form builder, then you should consider taking this opportunity to revisit your form within the new form builder instead.
I have PayBridge, will my payments work with new forms?
Yes payments are supported in the new form builder and can be used on both legacy and new forms.
Will my form URLs need to change in the new form builder?
Legacy forms will continue to be served from /forms/form/[id]/[lang]/[title] urls.
Forms built in the new form builder will be served from /xfp/form/[id] urls.
I have made changes to my front end scripts, how do I re-apply these changes?
Any front end changes that you have made will not be compatible with the new form builder. The new form builder uses Photon templating, to re-apply any front end script changes you will need to extend the templates. Advice on how to do that can be provided on request.
I have custom developments in progress, do I need to pay for these to be changed to the new form builder?
Possibly, we would advise you to check your quote to see if allowance for the new form builder version has specified. If your quote specifically states the form builder version that the integration will be developed for there maybe an additional cost to update the integration to support the new form builder.
What will happen once I build new forms, then turn off the new form builder? Will my new forms disappear?
No the form definitions will remain in the database until the new form builder is turned back on.
When I migrate old forms to the new forms builder, what will happen to existing submitted form data?
The submitted form data will remain accessible via the legacy form builder until data retention policies remove the data. Tools such as Data Export can continue to be used to export the data as required.
Features
I used to use this feature, why isn’t it in the new form builder?
Some features have been retired in the new form builder, in the majority of cases there is now a better, easier way to perform the same function. For example you’ll notice that there is no longer a Table component. This has been replaced by two page elements; a matrix page element that displays a structured table and repeatable questions, that provide a more mobile friendly way of populating tabular data.
The new form builder does not include the password component or PHP calculations. These have been retired for security reasons.
If you used to use a feature that you can’t find anymore or just not sure if an alternative exists within the new form builder, then please do get in touch with us to discuss.
When is feature X coming to the new form builder?
If the feature was part of the legacy form builder, for example embedded forms, these features will be added to the new form builder over the coming releases and well before the legacy form builder is removed at the end of 2020.
To see what we have coming up and what features we are working on, take a look at the XFP roadmap. If the feature isn’t there yet, raise a feature request so that we can consider it.
What are the benefits of the new form builder?
Have a look at the form builder feature comparison matrix that we’ve put together.
What can I do now that I couldn’t do before?
Have a look at the form builder feature comparison matrix that we’ve put together for you.
Is there a feature comparison matrix so I can see what features differ between the form builders?
Yes, it can be viewed here.
There used to be workflow on received forms, where has that gone?
Received form data workflow has not been added into the new form builder. We found that many customers did not use the workflow in received forms and would often request that forms be marked as ‘Completed - Approved’ immediately on submission. The decision was made to not add this in to the new version therefore. If you have received data workflow needs then we suggest that you look at the Jadu CXM service that allows you to build and manage cases through a fully configurable workflow.
I currently have integrations configured, will these still work with the new form builder?
All core integrations via the IntegrationsHub such as Bartec Collective, Office 365, SinglePoint address lookup etc… are enabled in the new form builder and you do not need to make changes to the current integration.
Some form actions (Perceptive content and AssureSign electronic signature) have not been enabled in the new form builder just yet, but when they are, there will not be a need to update the integration settings.
Are the forms still accessible?
Yes forms are still accessible.
Do the features of the new form builder help me to be GDPR compliant?
Not initially, GDPR features will however be introduced during April 2018.
Are the forms still mobile responsive designed?
Yes they are.
Can I use images in my form for choice options (e.g. recycling boxes/coloured bins)?
No we don’t have a page element for that at the moment, this feature is on the XFP roadmap and will be added in a future XFP release.
Page elements are now much easier to develop and this could be achieved via a custom development if you so wished.
Can I now create multiple pdfs from a form now?
Yes, this is now possible in the new form builder.
If I change a page template does it now update all forms where that template has been used?
Yes. Pages can now be used on one or more forms, if you edit a page that is shared with more than one form you (or a higher level administrator) will be asked to approve the changes before they are reflected on the forms that use that page.
And of course if you later decide to revert the change, you can rollback to the previous version of that page.
Misc
Are the forms available in the Jadu Library compatible with the new form builder?
Some forms on the library will not be compatible with the new form builder, but they can still be downloaded and imported into the legacy form builder.
Forms compatible with the new form builder will end in a .zip extension whereas forms compatible with the legacy form builder will end with .tar extension. XFP’s import page will detect the type of file and use the appropriate import routine to import the form.
What security testing have you done?
Jadu uses Checkmarx to perform static code analysis of the Continuum code base, configured for OWASP Top 10 vulnerabilities. Code analysis takes place before every release and issues discovered are resolved before the release goes ahead.
Do you need Photon for the new front-end templates?
No, although forms built with the new form builder will use Photon behind the scenes to render the front end view, you do not need a Photon implementation to use the new forms.
