App Version Upgrades

i.e. When the developer adds a new widget(s) without any settings on visibility into form, after deployment, both new and old record(s) will share the latest form layout.

i.e. When the developer adds a new widget(s) with visibility setting (e.g. submission date < deployment date) into form, the new widget(s) will not be shown in the old record.

i.e. When the developer adds a new widget(s) and deploys with visibility settings for all/ most of the old widget(s) (e.g. submission date < deployment date), the old widget(s) will not be shown in the new record(s).

i.e. When the developer adds a new workflow state(s), after deployment, the old record(s) in “Editing” state will go through “Verification” for approval; and the old record(s) in “HR Approval” state will go to the ‘End’ state. 

For new submission, it’ll go through all states for approval.

i.e. When the developer deploys a new workflow state combined with the Diverter setting with the condition (e.g. submission date < deployment date), the old record(s) in “Editing” state will skip to “HR Approval”.

For new submission, it’ll go to ‘Verification’ and ‘HR Approval’.

i.e. When the developer deploys a new workflow state combined with the Diverter setting with the condition after “Start” state, for an old record(s), it’ll go through the existing workflow for approval until the end. 

For new submission, it’ll go through for all new states for approval and skip all old states

i.e. When the developer adds a new widget(s) into the PDF report, after deployment, both new and old records will share the latest form layout. However, the old record’s PDF file will show an  empty value in the new widget(s). 

i.e. When the developer adds a new widget(s) into new/ copied PDF report and applies with visibility setting (e.g. submission date < deployment date) on PDF widget in form, the new/ copied PDF report will be shown for a new submission, and it keeps the old layout for the old record(s).

i.e. When the developer adds a new widget(s) into new/ copied PDF report and applies with visibility setting (e.g. submission date < deployment date) on PDF widget in form, the new/ copied PDF report will be shown for a new submission, and it keeps the old layout for the old record(s).

i.e. When the developer deletes widget(s) in form, the value of the deleted widget(s) in the old record(s) is still kept in the database. However, the deleted widget(s) can’t be selected to show in any table view.

i.e. When the developer deletes state(s) in workflow, the old record(s) being in the deleted state(s) is rolled back to "Saved” state.

i.e. When the developer deletes the widget(s) into the PDF report, then those deleted widgets will not be shown in layout. If the developer wants to keep both versions of the PDF report, the developer can apply the amendment on the new/ copied PDF report. 

Existing Conditions

i.e. The new condition can be added directly, and the logic will apply to the new record;

The value on old records will not be affected until the widget is triggered again

i.e. The new condition can be added directly, and the logic will apply to the new record;

The value on old records will not be affected no matter that the widget is triggered again, if the new conditions are applied with time concept.

(e.g. submission date < deployment date

i.e. Due to complexity and maintenance issues, new widgets are recommended to be added for new logic checking (widget B) & to concatenate with (widget C) existing checking widget (widget A).

The logic will apply to the new record; The value on old records will not be affected no matter that the widget is triggered again, if the new conditions are applied with time concept.

(e.g. submission date < deployment date)