Scenario
Create a dynamic model:
- table name: test_embed_versioned_recs
- fields: test1 test2 activity_log_player_contact_test_embed_versioned_rec_id
- must be "versioned" (
_configurations.use_current_version: false may prove this)
Create a second dynamic model:
- table name: test_embed_unversioned_recs
- fields: test1 test2 activity_log_player_contact_test_embed_unversioned_rec_id
- must not be "versioned" and should use
_configurations.use_current_version: true
Create an activity log with two activities:
- item type: player_contacts
- process name: test_embed
In the options for the activity:
test_activity_versioned:
embed: dynamic_model__test_embed_versioned_recs
test_activity_unversioned:
embed: dynamic_model__test_embed_unversioned_recs
Add the appropriate user access controls to allow the user to create these resources. Add a page layout to show the master panel for the activity log resource.
Now go to the user UI, view a master record, expand the activity log panel, and add an item for the versioned activity. Enter details into the embedded form (test1 and test2 fields). When saved, the form should show in read only mode. It doesn't appear. If you edit the activity, the edit form correctly shows. On saving or cancelling, the show mode form is not present.
In the browser JS console, you are likely to see logged messages like fpa_state_item: could not find template_config dynamic_model__test_embed_item_recs v123
Repeating the same for the unversioned activity and the form likely shows correctly.
NOTE: this is test scenario is based on observations of a production server that indicates the error related to dynamic models that have "definition versioning: version at record creation".
Acceptance tests must show that embedded dynamic models for versioned and unversioned work correctly and view in edit and show modes.
To avoid regressions, we must also test an activity log activity that has a references config with a single entry, so that the item appears embedded, even though it is referenced through model references.
Scenario
Create a dynamic model:
_configurations.use_current_version: falsemay prove this)Create a second dynamic model:
_configurations.use_current_version: trueCreate an activity log with two activities:
In the options for the activity:
Add the appropriate user access controls to allow the user to create these resources. Add a page layout to show the master panel for the activity log resource.
Now go to the user UI, view a master record, expand the activity log panel, and add an item for the versioned activity. Enter details into the embedded form (test1 and test2 fields). When saved, the form should show in read only mode. It doesn't appear. If you edit the activity, the edit form correctly shows. On saving or cancelling, the show mode form is not present.
In the browser JS console, you are likely to see logged messages like
fpa_state_item: could not find template_config dynamic_model__test_embed_item_recs v123Repeating the same for the unversioned activity and the form likely shows correctly.
NOTE: this is test scenario is based on observations of a production server that indicates the error related to dynamic models that have "definition versioning: version at record creation".
Acceptance tests must show that embedded dynamic models for versioned and unversioned work correctly and view in edit and show modes.
To avoid regressions, we must also test an activity log activity that has a
referencesconfig with a single entry, so that the item appears embedded, even though it is referenced through model references.