Run this simple app on your Merative:tm: Social Program Management (SPM) installation to identify and extract any custom UI configuration in your project. This information is useful to SPM, to help us to plan and support the evolution of the SPM UI. It is useful for you, to help you to efficiently update or upgrade the SPM UI for your project.
The app ignores the standard locations that contain the default SPM UI configuration files, and searches for custom CSS, JavaScript, and domain Java:tm: renderer files in the project.
Note: For privacy and security, no other information is extracted and no information is requested from any database in the system.
The custom files are copied into an archive file, so you can copy them to a local development environment to recreate the customisation.
You’ll need node.js 10 or later to run the app.
Download and extract the app, which consists of the configuration.json and index.js files.
Run npm install to install the dependencies.
The configuration.json configuration file defines the paths to the EJBServer/components and webclient/components folders of your SPM installation. The skipComponents attribute defines which components to skip during the search. By default, it is set to skip all OOTB SPM components.
Run the app with the following command from the extracted directory:
node index.js
The custom files are copied into the Results directory. The file struture of the copied files is retained, so you can copy them into your local development environment.
-
For CSS and JavaScript files, we copy any files with the extensions
.cssand.js. These are mainly in thewebclientcomponent, but we also search theEJBServercomponent for IEG customisations, which are in theEJBServer/component/***/datadirectory. For example,EJBServer/component/***/data/my-custom.css. -
For domain renderers, we search for files called
DomainsConfig.xml, find instances ofview-renderer,edit-renderer, orselect-renderer, and copy the associated Java file that is defined in theclassattribute.