...
An incredibly powerful aspect of ClinSpark is the ability to customize reports and dashboard components in both a modular and controlled way. Customers can even request that Foundry Health develop new or ‘custom’ reports. More details about that process are outlined in this help article.
System configurations also receive regular updates over time as enhancements are routinely made, sometimes necessary with new features that are developed. For example, when improved password reset features were implemented, a new set of configurations were added that allows for the customization of alert messages that are emailed to users.
...
Foundry Health maintains ‘least common denominator’ settings that are automatically pushed to environments upon initial deployment. During customer onboarding these are commonly referred as ‘bootstrapped’ configurations which are provided to all customers by default. In the example of password reset, this would include the default email template used when sending password reset emails, when customers accept that build into an environment.
Synchronization States
The A synchronization feature is available to superadmin users through a set of visual cues and descriptors that reflect the known state of a given configuration. These are important to understand as they serve a different purpose and meaning depending on the state of the environment, and, what actions can be taken against the configuration.
...
Each configuration will display to users a status message indicating if action is required. Within customer environments, each Each configuration should be looked at carefully with each status message to determine what the appropriate action is. If there is ever a question on whether or not a configuration should be modified, seek the assistance of engineering to confirm what exists in the deployed environment and what is in the project source.
Configuration Synchronized
...
The Import action takes the View(GSP) and Data(Groovy) script values from the configuration present in the deployed WAR file, override the previously supplied values, and offer user a chance to save the changes with an audit reason.
...
This status message informs users that a configuration exists in the database, but it’s not mapped to any known configuration within the deployed WAR file. While there may not be any action to be taken for this, the presence of unknown configurations could be addressed with engineering help to determine if any action is required.
...
This status message alerts Foundry Health users superamins to the fact that a configuration setting exists in the deployed WAR, but it’s not yet saved to the database, and therefore is not visible or accessible to customers.
This is often the result of newly developed global configurations such as reports, dashboard components, or volunteer search functions that become present in newer deployments of ClinSpark, but have not yet enabled for use.
When a configuration requires prompts for save, it should be considered if the customer needs the configuration. Some customers may not need those items as it would not be applicable to their current use of the system, or, they have not yet had the chance to review the specifications of the configuration change before accepting it into their environment.