Improved programs module customization

Thanks for providing detailed examples and the scenarios.

We have reviewed this and acknowleding that there are certain restrictions when it comes to the customisation of certain fields in the Programs module. In particular, the Status/Type/Class/Priority fields are generally fields used by platform's standard power reports, and cannot be renamed without breaking the reports.

For changing of field orders, drop down values, custom calculations, custom validations and hiding of fields, these can reviewed and done by IBM if they are deemed feasible. Please continue to engage us by raising IBM support tickets should any of these changes are further required.

We will further assess and consider in future roadmaps to make the advanced cusomisation available to end users.

During our Envizi implementation, we needed to change a number of settings in the Action fields to match our organisational requirements. This was only possible with the assistance of an IBM Envizi expert, and we believe the module would benefit from this customisation being available to the user. There are some customisable fields as standard, but changing fields built in, such as Priority, proved troublesome, and had impacts in other areas.

Examples of changes we implemented were:

·       Changing of field names

·       Changing of field orders

·       Changing of dropdown lists

·       Custom calculations using field entries

Changing some of these has impacted the standard PowerReports, which is currently being investigated by IBM. (Priority field was changed to reflect different organisation specific metrics and does not reflect changes in PowerReports) Any changes should be carried through to the reports.

There were also certain restrictions in the current version of the module which we believe could be improved. We structured our Action creation process/field order to reflect the stages of our projects from initial project scoping details (location, type, estimated savings, timelines) to actual project metrics, and finally M&V details. Would it be possible to hide certain fields depending on earlier entries? For example, selecting a project type – Lighting rather than Heat Pump, would require the user to populate certain project type specific fields and hide non-specific types.

Hi Ian, can you please provide some detail and examples? The programs module supports customisation so we're keen to better understand you specific asks/needs. Thanks