servoy / svybase

Base forms for servoy

svyBase

THIS MODULE IS IN ALPHA AND IS EXPERIMENTAL. USE AT YOU OWN RISK.

The module is designed to provide easy-to-use Servoy base forms and related functionality for implementing data entry (create/update/delete - CRUD) forms for business applications.

svybase's Issues

onRecordSelectionHandler does not fire on child forms when no records available

There is an issue in the following circumstance:

• master/detail-form-scenario
• you're on a master-record that has some detail-records
• then jump on a master-record that has no detail-records
  => onRecordSelectionHandler and updateUI doesn't fire on the child-form! But these events should also fire here!

This happens in "svyBaseCRUD" on line 1321 and following. In this case the variable "fireHandler" stays null and because of that "applySuper('onRecordSelectionHandler'...)" will not be executed.

I18n

Strings / Messages should be i18n, please.

Save-Issue in parent-child-situation when deleting a record on child form

Hi

We have the following issue:

Our settings:

policy.setBatchScopePolicy(scopes.svyCRUDManager.BATCH_SCOPE_POLICY.ALL);
policy.setRecordLockingPolicy(scopes.svyCRUDManager.RECORD_LOCKING_POLICY.NONE)
policy.setValidationPolicy(scopes.svyCRUDManager.VALIDATION_POLICY.CONTINUOUS);
policy.setFormHidePolicy(scopes.svyCRUDManager.FORM_HIDE_POLICY.ALLOW_WHEN_EDITING);

As an addition for parent forms: policy.setRecordSelectionPolicy(scopes.svyCRUDManager.RECORD_SELECTION_POLICY.PREVENT_WHEN_EDITING);

and for child forms:
policy.setRecordSelectionPolicy(scopes.svyCRUDManager.RECORD_SELECTION_POLICY.ALLOW_WHEN_EDITING);

Situation: we have a parent form and a child form. Save of all records (parent and child forms) always happens on the parent form.

We do the following steps:

• Add a new record on the parent form (don't save)
• Add a new record on the child form (don't save)
• Delete the record on the child form

This leads to the situation that the record on the parent form is saved (not in create-mode anymore)! The record is not stored in the database but it looks to the user as the record is stored, even if validation failed. So the user must reload the parent form data or delete the record in parent form.

Expectation: if the user deletes a record in the child form, the parent form must remain in its state!

Thanks in advance!

Best
Roland