In the article, I described a measure to enhance the visibility of the Workflow diagram by reducing the number of Steps, such as;
...In addition, "Service Task (Data assignment)" is capable of assigning a value to multiple Data Items at single Step. In case if multiple "Service Task (Data assignment)" are arranged consecutively, please consider consolidating them into one...
In the article, I described a measure to enhance the visibility of the Workflow diagram by reducing the number of Steps, such as;
...In addition, "Service Task (Data assignment)" is capable of assigning a value to multiple Data Items at single Step. In case if multiple "Service Task (Data assignment)" are arranged consecutively, please consider consolidating them into one...
As I might be asked by someone saying "So, how can I concretely do?", so let's try to rewrite the Workflow diagram of the past together actually.
[Billing-Payment Confirmation flow 1]
[Billing-Payment Confirmation flow 1 (Integrated Steps)]
You understand that multiple consecutive "Service Tasks (Data assignment)" are integrated into one Step, and the Workflow diagram has become neatly. In the Workflow diagram of "after integration", the Step (human task) that people operate is more noticeable, and it is easy to understand for the person in charge of operating as well.
On the other hand, since multiple processing is done in the auto-step (Service Task (Data assignment)), the contents of each processing are a little difficult to understand. This may also be true if you are processing with a script using "Script Task", or when using "Service Task (Add-on)". It is necessary to devise a way how you name the automatic Step.
In the Step of "Title, filename, etc. set", inputting to Data Items is done automatically. There, "Data setting formula" that I introduced in the article before is also active.
- Set Date/DateTime by specifying format
- #{#format(data[25] , 'yyyy年MM月dd日')}
- With "Invoice Issuance Date" alone, it would be "2018-07-17"
- Specifying its format to "2018年07月17日", then set it into "= Date Indication"
- Set the Date/DateTime of being proccessed
- #now/#today
- 2 hours and 30 minutes later: #now.addHours(2).addMinutes(30)
- 5th of the next month: #today.getFirstTimeInMonth().addDays(4)
- Set "Invoice Filename" according with "Process ID", etc.
- Invoice-p#{#sformat('%05d', processInstanceId)}-#{#format(data[39], 'yyyyMMddHHmm')}-#{#format(data[28], 'yyyyMMdd')}.pdf
- 5 digit indication on Process ID: #sformat('%05d', processInstanceId)}
- In case where Process ID has only 3 digits, "0" are inserted at the top e.g. 00123
- Variables such as Process sequence number (#{processInstanceSequenceNumber}) or App name (#{processModelInfoName}) are also available
- Utilization of Functions (Not used in the Business template in this article)
- Generate random alphanumeric character string of specified number of characters: #{#randomString(12)}
- Generate a Hash string out of "Title": #{#escapeEcmaScript(data['1'])}
- Generate an XML escaped string: #{#escapeXml(data['2'])}
- Clearing value (Not used in the Business template in this article)
- Possible to clear an entered value by setting nothing (blank) in "Value or Expression"
["Title, filename, etc. set" setting screen]
Similar Models
- Non-payment! Automatically Escalation! (2014-11-10)
- Cooperation of Invoicing Flow and Accounting System (2015-04-27)
- Setting the Title of Issues with Auto-processing Script (2014-07-22)
Free download
Business Template : Billing-Payment Confirmation flow 1 (Integrated Steps)Related Articles
- M227 (AUTOMATED STEP) Auto Executing Data Binding, Arithmetic Operations (Manual)
- M228 (AUTOMATED STEP) Auto Generating PDF File with Business data Inserted (Manual)
- M403 (DATA ITEMS) Setting: Strings to which Business Data has been Inserted to be Set in Midstream (Manual)