...
At design-time, when connected to an open model edition deployed in a development data location, changes that only impact the application UI (for example, modifying a form view or a workflow) do not require an update of the deployed model edition.
The application browser window can be refreshed (F5click your profile in the top right and select 'Refresh application') in order to dynamically regenerate the application UI and see the changes.
An Update of the deployed model edition is necessary when either the model structure (entities, attributes, references, etc) or rules (enrichers, matchers, etc).
| Info |
|---|
If the model structure or rules have been modified, a browser refresh made without a model update may cause the application to behave unexpectedly. For example:
|
If the changes do not reflect correctly in the application, or if the application behaves unexpectedly, it is recommended to:
- Validate the Model and fix possible validation errors
- Update the deployed model edition, making sure to update both the jobs definitions and database schema.
- Refresh the application browser window.
At Run-Time
...
| Panel | ||
|---|---|---|
| ||
Here is an example where there are 2 open model editions: However, in the Data Location, the deployed model is CustomerAndFinancialMDM [0.0] not CustomerAndFinancialMDM2 [0.0]:
Therefore, any changes made to CustomerAndFinancialMDM2 [0.0] will not be seen in the Application UI. |
...
- Full information about deployment is available at the following URL: http://www.semarchy.com/doc/semarchy-mdm/semdg.html#deployment
...