BPMs Form Version Control design

Because the form designer satisfies form modifications (additions and deletions) during the run, the form version control does not need to be modified specifically. If you still want to control, it should be a different form version corresponding to different HTML, and then the database table name unchanged form. Versioning also loses its meaning if a new table is available for each published form version.

It is recommended that the form versioning is still in the existing scenario and does not change.

First,Form Version Control1.1no problems with form versioning

With the recent turnover order update as an example, the new version of the separation order has increased the department sign-off function, the original online down the administrative,IT, Finance, college approval online. The new version is not only the process of re-planning, the form is also very large, such as the addition of the signing and whether it is necessary to fulfill the competition agreement, the department signed the comments filled and so on. Under the effective control of the process version management, the new and old version of the process can work normally, but there is a conflict in the form. To ensure coordination between the old and new versions, the temporary solution is to preserve the visibility of all process instances in the old and new versions of the field before and after the modification. The biggest flaw is the new and old version of the style and fields tangled together, disorderly, user experience is very poor.

2.2. Solution for form version Management

The so-called version management, is the management of version identification, so that the forms between different versions of each other, non-interference or have a certain degree of mutual compatibility. OA the management of the form version is to be independent of each other, without interference.

The scenario is as follows: Build a version table for the form to hold historical version information (including the latest version information), and the latest version information is stored in the form definition table. The form version information is taken out when the process is initiated and approved,Fromdefineidshould be replaced by the correspondingVerid. For compatibility with non-versioned processes: such as versionIDIs empty, then takeFormdefinetable in the latestFormdefineidThe correspondingHTML,Template. The setting of the form permission must beVeridfor identification purposes, notFormdefineidfor identification.

Defects in form management scenarios: updates to forms are more frequent than versions, which greatly increases the amount of task that development and operations personnel maintain form permission tables.

Workaround for defects: The update of the form version should not be like a process version update, and each release will inevitably produce a new version. When you click on the form to save, the selection box should pop up and the development or OPS person decides whether to publish a new form version or not to publish a new one. If you publish a new version, you need to maintain the form permissions, if you just JS or add hidden fields, modify styles, you can choose not to publish a new version, the saved action does not update the version number.

2.3.1 Creating a Form History version table T_bpm_form_version

Field name	Field type	Constraints	Note
Id	varchar		Version ID
Formdefineid	varchar		The form identifies
html
template
Talbedefineid			entity table id

2.3.2 T_bpm_form_define Add a column of version(currently present)

2.3.3t_bpm_process_execution Add the version field as an identity to load the form

2.3.4 most currently known action are dojob dojob as the entrance, and all the querybyformdefineid and formdefineentity.gethtml

Risk: The change involves a large area, more changes, the need for comprehensive testing.

The final scenario uses the form versioning scheme described in this document.

This article is from the "Jiangnan Miner Technology Space" blog, please be sure to keep this source http://jncumter.blog.51cto.com/812546/1746247

BPMs Form Version Control design