This page answers frequently asked questions about our rendering engines for web interfaces, Application Runner and WIRE.
What are the differences between Application Runner and WIRE?
WIRE offers many advantages related to user experience, development productivity, performance, and sustainability.
The differences, which you have to take into account when designing and configuring web interfaces with their widgets, are described in detail in Differences Between Rendering Engines.
When will I get access to WIRE?
Starting in autumn 2021, WIRE will be made available step by step to more and more customers in addition to Application Runner. If you are interested in using WIRE, please contact the RunMyProcess support.
Where can I select the rendering engine for a web interface?
You can select the rendering engine when you create a web interface. As a prerequisite, WIRE must have been enabled in addition to Application Runner for your customer account.
Where can I see which rendering engine a web interface is using?
In DigitalSuite Studio, the web interface lists of the Project Configuration and Resources modules show the rendering engine of each web interface in the left-most column: While the column is empty for web interfaces based on Application Runner, the following icon is displayed for WIRE based web interfaces:
The rendering engine is also displayed in the settings of each web interface on the Settings tab.
Can I change the rendering engine for an existing web interface?
At the moment, it is not possible to change the rendering engine for an existing web interface or to directly migrate a web interface from Application Runner to WIRE, or vice versa.
Of course, you can at any time re-create a web interface with the desired rendering engine.
Do I need to migrate my web interfaces to WIRE?
At the moment, there is no need to change your existing web interfaces that rely on Application Runner. A project in DigitalSuite may include web interfaces based on Application Runner as well as web interfaces based on WIRE.
However, since WIRE offers many advantages compared to Application Runner, you should consider to create new web interfaces based on WIRE.
How would I proceed to migrate my web interfaces to WIRE?
At the moment, you cannot migrate web interfaces directly from Application Runner to WIRE. However, you can at any time re-create your Application Runner based web interfaces to use WIRE as the rendering engine.
There are two basic ways of how to proceed:
- Using a new project: Create a new project, copy the resources except for the Application Runner based web interfaces from the original project to it, and re-create the web interfaces in the new project based on WIRE. This way is preferable for medium-size and big projects with several web interfaces. It gives you all the time you need for checks, clean-ups, and adjustments not only of the web interfaces themselves but also of related resources. After you have sorted out all issues, you can switch to the new project and remove or keep the original one as desired.
- Using the existing project: Re-create the web interfaces one by one in their existing project and adapt references to them as required. After you have successfully tested the application with the WIRE based web interfaces, you can delete the Application Runner based ones. This way is suitable for small projects and faster than using a new project.
Can I use different rendering engines in the same project or process?
A project in DigitalSuite may include web interfaces based on Application Runner as well as web interfaces based on WIRE.
However, all web interfaces used by a process should be based on the same type of rendering engine, Application Runner or WIRE. A WIRE based web interface cannot load the next screen upon a button click, if this next screen belongs to a web interface based on Application Runner, and vice versa.