Last updated Sep 12, 2017

Initial Value of Data Items Set at the Start

You can configure a "state in which the data is input in advance". You can define an initial value that varies by operating person or by the date and time of Process Started as well as a fixed value, such as "the Applicant's Name", or "date of 14 days later from the application".


1. Illustration of Example
Preventing “fluctuation” of the input format (e.g.: ●●,Inc.)
2. Automating of Standard Value Input
Reducing the labor of inputting the same value (the standard value) (e.g.: Your Designated Place)
3. Automating Compliance with the Business Rule
Saving the computation time of a value based on the business rules (e.g.: Enter due date at end of the following month)
  • Extensive use of the Initial Value might increase the risk like “believing to have input”, etc.
  • You can also set input guidance texts (HTML5, placeholder), instead of an initial value (in String type, etc.)
a. Fixed Value Preset
e.g: ‘Your Designated Place’ (String type), ‘2020-07-24 20:00’ (Datetime type)
  • If a wrong value is assigned, the initial value will be ignored (e.g.: ‘2001-02-29’ in Date type)
  • You can not set initial value in File type, Discussion type, Table type, etc.
R2052 Format of the Fixed Initial Value (Subtype List)
b. Preset of Referring to Start Time
e.g.: Set the last day of the following month to the item of “Payment Period”
c. Preset of Referring to Start User
e.g.: Set a title that includes the applicant’s Name
d. Preset of Referring to Workflow ID
e.g.: Set a filename that includes sequence number
  • Depending on the data type to be assigned, the setting method of an assignment and data that can be referenced are different
R2053 Format of the Dynamic Initial Value (Subtype List)
a. unknown Organization
[Started Organization] of [Newly started] by Users who belong to multiple Organizations
b. Unknown Starter
[Started User] of an Issue which the first Step becomes [Waiting Underwriting], such as Timer Start, etc