We have a series of custom form components that were designed by Appian for our

garethm over 11 years ago

We have a series of custom form components that were designed by Appian for our repairStream system, which have been working in Appian 6.1.

I am working on an upgrade to 6.6.1, and although all the customised files appear to me been moved across to the new environment, the components themselves are not working.

The custom menu bar is shown, with the 4 components, however when attempting to add any of them to a form, a single blank row is generated, that can not be selected.

From looking at the instructions for creating custom components in both 6.1 and 6.6.1 (which are identical) there seems to be a file missing - the control templates - but these are not present in the working 6.1 environment...

Any thoughts / solutions on how I can resolve this issue ?

Many thanks

Gareth...

Discussion posts and replies are publicly visible

0 meghan.mahar
Appian Employee
over 11 years ago

I noticed in the "Converting Custom JSPs, Servlets, or Action Paths" of the Migration Guide, it mentions <APPIAN_HOME>/ear/suite.ear/web.war/forms/templates/config/ as on Old Directory and <APPIAN_HOME>/ear/suite.ear/web.war/forms/templates/config/custom/ as the one to use instead. I wonder if the control template needs to be added to that folder instead.

For reference: forum.appian.com/.../Appian_6.6.1_Migration_Guide

If that works, I can update the documentation for Creating the Control Template to reflect the correct file location for the control template: forum.appian.com/.../Developing_Custom_Forms_Designer_Components
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 meghan.mahar
Appian Employee
over 11 years ago

Then again, you say the control template didn't exist in the 6.1 environment?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 garethm over 11 years ago

Thanks Megan, I hadn't spotted that difference.
There are no control templates, but further digging has lead to them refering to a Picker3 - which does have customisations in the 6.1 environment... but the ANT build did not replicate.
Hopefully merging the custom scripts into the 6.6.1 files will solve the problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel