Best practices for Portal Page Developers
Do Portal Pages inherit CSS from the rest of the application?
If setting "Catalog Layout" is set to "yes", a Portal page inherits all styles from the application, including its theme (if applicable).
To use custom CSS classes, we recommend adding a prefix
cp_ (custom page) in front of new class names. iframes can be used to prevent CSS overlaps from happening.
- jQuery must be used in no-conflict mode
- Highcharts v5.0.4 and Underscore.js version 1.8.3 are available globally
- Ext.js is not allowed
As of Metric Insights 6.1.0, Portal Page developers can utilize the following methods:
storeData()will it store states in JSON format
getData()will display data about state that was previously saved
All state-related data saved in the
portal_page_data table within
States can be global or localized to a specific user via a
per_user_ind Y/N boolean. The default is set to global (N)
How should I manage my assets?
Note: You are not able to reference externally hosted libraries. They must be hosted within the MI system itself. We enforce this to meet common security requirements in the enterprise.
If I use a custom theme, how do I apply those colors/styling to my portal page?
- If "Catalog Layout" is set to "yes", the theme will be applied automatically.
- If "Catalog Layout" is set to "no", the developer should explicitly include theme CSS in their layout.