Customizing App Studio
The App Studio explorer is built using the data driven UI framework. To learn more about this framework, please read the article Data-driven UI framework.
The abstract class Pega-Ext-ExpExplorer is extended from Pega-Ext to build the App Studio explorer. The four default tabs seen on the App Explorer are subclasses under Pega-Ext-ExpExplorer.
Pega-Ext-ExpExplorer-Case
Case items are dynamic
Pega-Ext-ExpExplorer-Data
Data items are dynamic
Pega-Ext-ExpExplorer-Settings
Pega-Ext-ExpExplorer-Settings-Theme
Pega-Ext-ExpExplorer-Settings-Tools
Pega-Ext-ExpExplorer-User
Pega-Ext-ExpExplorer-User-People
Pega-Ext-ExpExplorer-User-Roles
Pega-Ext-ExpExplorer-User-Organization
Add extensions
To extend App Studio explorer, add an abstract under Pega-Ext-ExpExplorer. Follow the steps detailed out in the Data driven UI framework article. Ensure you place the class at the correct depth to ensure that the page shows up at the correct depth.
Implementation details
A dynamic container is used to launch the extensions in a landing page. At most, there will be two landing page tabs. The default page is LiveComposer which is the case manager/user portal in edit mode. The other tab is EditModeExpressTab which is used to open pages such as case and theme. If an extension landing page is clicked, it will replace the content in EditModeExpressTab.
To configure this behavior for the extension, make the following edits in pyExpExplorerSliderLabel.
- Add the exp.Slider.closeSlider run script to close the slider.
- Configure Launch Harness action to label control.
- Enter tab name as EditModeExpressTab.
- Use the template harness pzExpressLPHarness to create your own harness.
- Set the data transform as pzSetExpressSkinForEditMode to override the end user skin.
- Set the activity pzPreLPActivity as the preprocessing activity before launching your landing page.
Extension points
- Override pyExpressLPHeaderTitle to populate the landing page header dynamically.
- Override pyExpressLPContentTemplate to show custom content in your landing page.
Previous topic Data-driven UI framework Next topic Extending the New Application wizard