This article explains how to avoid issues in Lumary that may be caused by adjusting an environment's Salesforce configuration or settings.
Lumary uses managed packages on the Salesforce platform. This allows for flexible solutions tailored to specific business needs. However, changing some Salesforce options may cause issues within Lumary solutions.
The following table provides a list of settings and recommendations. These settings should not be modified without explicit instruction from Lumary. Lumary does not take responsibility for issues caused by changes made to these settings by:
- customers, or
- third party consultants.
| Setting | Recommendation |
|---|---|
| Flows |
Enabling or disabling flows after Lumary installation may cause unexpected behaviour. This can impact
To ensure system stability and proper functionality, consult the Lumary support team before making any changes to flow configurations. |
| Triggers |
While it's not possible to disable or enable triggers through the user interface, it's crucial to note that no programmatic changes should ever be made to triggers associated with Lumary packaged objects by anyone outside of Lumary. Such modifications could severely impact system functionality and data integrity. Always consult with Lumary support for any trigger-related concerns or requirements. |
| Validation rules |
Validation rules should not be disabled without explicit instruction from Lumary. Disabling validation rules may allow users to save invalid data. This will impact the integrity of the data in the environment. It may also have unexpected impacts on other functionality. Some of Lumary's features rely on validation rules to work as intended. |