String type(!), Date type(!!), File type(?!), Discussion type(?!!)

Monday, February 24, 2014
'Input Form, How will it kook?'

'Input Form' is important for a Workflow system. Particularly, for the person in charge of [Process Modeling](*) at the scene, it worries that how the input screen would come along. You need to seriously think about, for example, what and where a precautionary statement should be described to help the colleagues of the organization. (* Object that the people in charge of the "Process Modeling" created -> Process Model)

With that said, the following is an experiencing sample of the input form. String type, Date type, File type... You can experience inputting into various [Data type items] at one time. Even though you can download only a template that can be imported to the cloud-based workflow "Questetra BPM Suite", "data input experience" might be essential In the selection process of the workflow product.

I am going to upload the template in the "Online Demo". However, because it could have been edited, you should better to import it to your "Free SaaS Edition" if you are a user. (Would not hurt.)

By the way, we have been continuing to provide 'samples' for three and a half years in this website "Workflow-Sample", but I think this article is so much not related to the 'business improvement' for the first time.

[Input Test]

[Input Test:'1. Input Test' screen]

[List of Process Data Item]

'Initial value setting' is helpful.
You can save the time of input because it has been filled in automatically before inputting... (As a matter of course)

In the Cloud-based Workflow "Questetra BPM Suite", you can set
  • R205-2: 'Static initial value', a value that does not vary even the instance has been started at any time, as well as
  • R205-3: 'Dynamic initial value', a value to be set varies by the started time or by the started user.

Also in this sample, the expressions of "dynamic initial value" like following have been set in the process model.

= You can set various format to the initial value of String type data item. =
The ID of this Process Model is #{processModelInfoId}.
The Name of this Process Model is #{processModelInfoName}.
This Process Model ID is #{processInstanceId}.
You can change the numeric format. You can also manage by the "Sequential number" on each process model. e.g. xyz#{#sformat('%06d', processInstanceSequenceNumber)}
You can set started date to the initial value OF a string type data item in a variety of formats as well. e.g. #{#format(processInstanceStartDatetime, 'yyyy-MM-dd, HH:mm')}

Actually, the specific "value" to be automatically set at the moment the Process started is,,, I think it's faster you get experience by Starting a new Process.

In addition, 'regular expression check' to one of 'String type data (single line)', 'dynamic indication of automatic calculation result' to one of 'Numeric type data' have been set in the sample respectively. "Small improvements", preventing erroneous input, is also important in business process management activities. (Rather, I should say "attentive correspondence" that stood in the worker side?)

Bythe way, if you want to use smart phone for the input of every day, it is essential to"experience" in the smartphone in practice. In comparison with the PC, it is still cumbersome, but, "anytime, anywhere" would become a hint of the corporate strategy. Knowing it is a hard way, you might better to "experience" it 10(!) ,100(!!) , 1000(!!!) times.

[Free Download]
<<Related Articles>>