tag:blogger.com,1999:blog-55663427052079616692024-03-12T22:23:49.409-04:00Workflow Sample<strong>Workflow Diagram Changes the Day-to-day Business!</strong><br>
A Blog site to publish Downloadable "Business Templates" weekly.imamurahttp://www.blogger.com/profile/16720179453783569372noreply@blogger.comBlogger597125tag:blogger.com,1999:blog-5566342705207961669.post-35080322300060155822018-12-26T19:00:00.000-05:002018-12-26T19:00:13.937-05:00Episode Final: Appreciation for Readers, and the Future<div class="separator" style="clear: both; text-align: center;">
<a href="https://3.bp.blogspot.com/-Yh2rY6BiQD4/XCLp5ASbRqI/AAAAAAAACY4/1xnRPoJRQLsjJJAvuVQ8CpPL-_I1hR3FQCLcBGAs/s1600/RiverStream3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="840" data-original-width="1600" height="336" src="https://3.bp.blogspot.com/-Yh2rY6BiQD4/XCLp5ASbRqI/AAAAAAAACY4/1xnRPoJRQLsjJJAvuVQ8CpPL-_I1hR3FQCLcBGAs/s640/RiverStream3.png" width="640" /></a></div>
<br />
<br />
Thank you very much for reading this blog for many years.<br />
<br />
Although this blog that has been on since 2010, we decided to continue on 2 sites below with a little change.<br />
<br />
<ul>
<li>Staff Blog (<a href="https://questetra.com/category/blog/" target="_blank">https://questetra.com/category/blog/</a>)<br />
For the general public, we will disseminate a wide range of contents on the agenda of Business improvement/BPM/Workflow.</li>
<li>Developers Blog (<a href="https://support.questetra.com/category/developer-blog/" target="_blank">https://support.questetra.com/category/developer-blog/</a>)<br />
Oriented for users of Questetra BPM Suite, we will disseminate specialized content for our service such as "How to create a Workflow Apps"</li>
</ul>
<br />
Regarding Business templates, we are planning to organize them on the page below.<br />
<ul>
<li>Business Templates (<a href="https://questetra.zendesk.com/hc/en-us/articles/360012492211" target="_blank">https://questetra.zendesk.com/hc/ja/articles/360012492211</a>)</li>
</ul>
<br />
We look forward to your continued support in the future.<br />
We wish everyone to have a good year!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-62176191107212895012018-07-16T01:54:00.000-04:002019-01-17T04:04:24.655-05:00Episode 596: Improve Workflow Diagram into Easy-to-see by Integrating Multiple Steps into One<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6577572634923493282" src="https://2.bp.blogspot.com/-MrVUaSITrjc/W0g7dkTx56I/AAAAAAAAMYo/UQKn9jaF7tc6jtDqVIowLZPS0N15VP9kQCK4BGAYYCw/s640/20180717-Billing-payment_Confirmation-770811.png" width="640" /></div>
In the previous article, "Episode 595: Alternate Method of Setting Expiration on Questionnaire", I have introduced "A method of setting a timer with Data setting formula".<br />
<br />
In the article, I described a measure to enhance the visibility of the Workflow diagram by reducing the number of Steps, such as;<br />
<br />
...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...<br />
<br />
In the article, I described a measure to enhance the visibility of the Workflow diagram by reducing the number of Steps, such as;<br />
<br />
...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...<br />
<br />
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.<br />
<br />
<div style="text-align: center;">
[Billing-Payment Confirmation flow 1]</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://3.bp.blogspot.com/-OvI8yUBLlwE/W0hADheyXoI/AAAAAAAAAYI/Uypd4668Mhg3HQRZ5glGJev9HAp1dxPrwCLcBGAs/s1600/20141110-1-en-733628.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="466" data-original-width="988" height="300" src="https://3.bp.blogspot.com/-OvI8yUBLlwE/W0hADheyXoI/AAAAAAAAAYI/Uypd4668Mhg3HQRZ5glGJev9HAp1dxPrwCLcBGAs/s640/20141110-1-en-733628.png" width="640" /></a></div>
<br />
<br />
<div style="text-align: center;">
[Billing-Payment Confirmation flow 1 (Integrated Steps)]</div>
<a href="http://4.bp.blogspot.com/-XstGyyaSwI0/W0g7dbqI-sI/AAAAAAAAMYQ/P1c-fMN5eDwKf_Pzgtn-kmfSW-hNNPtwwCK4BGAYYCw/s1600/Billing-Payment_Confirmation_flow-Integrated_Steps-app-en-769098.png"><img alt="" border="0" height="256" id="BLOGGER_PHOTO_ID_6577572632601361090" src="https://4.bp.blogspot.com/-XstGyyaSwI0/W0g7dbqI-sI/AAAAAAAAMYQ/P1c-fMN5eDwKf_Pzgtn-kmfSW-hNNPtwwCK4BGAYYCw/s640/Billing-Payment_Confirmation_flow-Integrated_Steps-app-en-769098.png" width="640" /></a><br />
<br />
<a name='more'></a><br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
<ul>
<li>Set Date/DateTime by specifying format</li>
<ul>
<li>#{#format(data[25] , 'yyyy年MM月dd日')}</li>
<li>With "Invoice Issuance Date" alone, it would be "2018-07-17"</li>
<li>Specifying its format to "2018年07月17日", then set it into "= Date Indication"</li>
</ul>
<li>Set the Date/DateTime of being proccessed</li>
<ul>
<li>#now/#today</li>
<li>2 hours and 30 minutes later: #now.addHours(2).addMinutes(30)</li>
<li>5th of the next month: #today.getFirstTimeInMonth().addDays(4)</li>
</ul>
<li>Set "Invoice Filename" according with "Process ID", etc.</li>
<ul>
<li>Invoice-p#{#sformat('%05d', processInstanceId)}-#{#format(data[39], 'yyyyMMddHHmm')}-#{#format(data[28], 'yyyyMMdd')}.pdf</li>
<li>5 digit indication on Process ID: #sformat('%05d', processInstanceId)}</li>
<ul>
<li>In case where Process ID has only 3 digits, "0" are inserted at the top e.g. 00123</li>
<li>Variables such as Process sequence number (#{processInstanceSequenceNumber}) or App name (#{processModelInfoName}) are also available</li>
</ul>
</ul>
<li>Utilization of Functions (Not used in the Business template in this article)</li>
<ul>
<li>Generate random alphanumeric character string of specified number of characters: #{#randomString(12)}</li>
<li>Generate a Hash string out of "Title": #{#escapeEcmaScript(data['1'])}</li>
<li>Generate an XML escaped string: #{#escapeXml(data['2'])}</li>
</ul>
<li>Clearing value (Not used in the Business template in this article)</li>
<li>Possible to clear an entered value by setting nothing (blank) in "Value or Expression"</li>
</ul>
<div style="text-align: center;">
["Title, filename, etc. set" setting screen]</div>
<a href="http://4.bp.blogspot.com/-_YYGTV2yWgE/W0g7dbs0n_I/AAAAAAAAMYg/uGkzmIEFVDge5xpE7k7wfBzJzLb-XOO7QCK4BGAYYCw/s1600/Billing-Payment_Confirmation_flow-Integrated_Steps-cap-en-769745.png"><img alt="" border="0" height="584" id="BLOGGER_PHOTO_ID_6577572632612610034" src="https://4.bp.blogspot.com/-_YYGTV2yWgE/W0g7dbs0n_I/AAAAAAAAMYg/uGkzmIEFVDge5xpE7k7wfBzJzLb-XOO7QCK4BGAYYCw/s640/Billing-Payment_Confirmation_flow-Integrated_Steps-cap-en-769745.png" width="640" /></a><br />
<br />
<h3>
Similar Models </h3>
<ul>
<li><a href="https://en.workflow-sample.net/2014/11/proceeding-by-timer.html">Non-payment! Automatically Escalation! (2014-11-10)</a></li>
<li><a href="https://en.workflow-sample.net/2015/04/invoicing-to-accounting.html">Cooperation of Invoicing Flow and Accounting System (2015-04-27) </a></li>
<li><a href="https://en.workflow-sample.net/2014/07/start-pattern-2.html">Setting the Title of Issues with Auto-processing Script (2014-07-22) </a></li>
</ul>
<n2><br />
</n2> <br />
<h3>
<n2>Free download</n2></h3>
Business Template : <a href="https://support.questetra.com/templates/20180717-billing-payment-confirmation/?dmy=.qar">Billing-Payment Confirmation flow 1 (Integrated Steps)</a><br />
<br />
<h3>
Related Articles</h3>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260571-M227">M227 (AUTOMATED STEP) Auto Executing Data Binding, Arithmetic Operations</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245612-M228">M228 (AUTOMATED STEP) Auto Generating PDF File with Business data Inserted</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002248232-M403">M403 (DATA ITEMS) Setting: Strings to which Business Data has been Inserted to be Set in Midstream</a> (Manual)</li>
</ul>
<div>
<br /></div>
(<a href="https://ja.workflow-sample.net/2018/07/Billing-PaymentConfirmation.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-3759756418784775582018-07-08T16:00:00.000-04:002018-07-12T00:24:57.653-04:00Episode 595: Alternate Method of Setting Expiration on Questionnaire<div class="mobile-photo"><img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6574659992048249410" src="https://3.bp.blogspot.com/-_8Yj2ZPPwx4/Wz3ibcECKkI/AAAAAAAAMWQ/FWK3ZjsaIKYCCnUw9qHXl7m0HV9ptD5bgCK4BGAYYCw/s640/201807-EventAcceptanceQuestionnaire3-717731.png" width="640" /></div><div class="mobile-photo">In the previous article, "Set Expiration to Post-Event Questionnaire", I have set "expiration to after 7 days" utilizing a Service Task. By setting a deadline for the questionnaire, it is possible to prevent the business process from staying stuck, even if it is not yet answered.</div><br />
<div style="text-align: center;">[Event_Acceptance-Questionnaire (Expiration)]</div><div class="separator" style="clear: both; text-align: center;"><a href="https://2.bp.blogspot.com/-U6qErOohunc/Wz7Ypv2XIyI/AAAAAAAAAXY/jHhfJ7_by4gPL5JRXuGOTbavLOZ1jWutACLcBGAs/s1600/20180702-Event_Acceptance-Questionnaire2-en.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="466" data-original-width="1215" height="244" src="https://2.bp.blogspot.com/-U6qErOohunc/Wz7Ypv2XIyI/AAAAAAAAAXY/jHhfJ7_by4gPL5JRXuGOTbavLOZ1jWutACLcBGAs/s640/20180702-Event_Acceptance-Questionnaire2-en.png" width="640" /></a></div><div class="separator" style="clear: both; text-align: center;"><br />
</div>For the setting of "after 7 days, "data setting formula is used.<br />
By writing "# now.addDays (7)", you can set "after 7 days" to "Expirtion (Date)" from the time (#now) when the token arrived in the "Expiration set" Step.<br />
<br />
<div style="text-align: center;"><"Expiration set" setting screen></div><a href="http://3.bp.blogspot.com/-w8ZRhApwA0w/Wz3icieJZPI/AAAAAAAAMW4/39Y6FVK5rSonHn1lBPvhkW39kK3hrlFpgCK4BGAYYCw/s1600/20180702-Event_Acceptance-Questionnaire-Expiration-setting-en-722535.png"><img alt="" border="0" height="584" id="BLOGGER_PHOTO_ID_6574660010948257010" src="https://3.bp.blogspot.com/-w8ZRhApwA0w/Wz3icieJZPI/AAAAAAAAMW4/39Y6FVK5rSonHn1lBPvhkW39kK3hrlFpgCK4BGAYYCw/s640/20180702-Event_Acceptance-Questionnaire-Expiration-setting-en-722535.png" width="640" /></a><br />
<br />
Other than that, in addition to the data setting formula expressing the date and time, there are;<br />
<ol><li>2 hours 30 minutes later: #now.addHours(2).addMinutes(30),</li>
<li>the end of the month: #now.getLastTimeInMonth(),</li>
<li>5th of the following month: #today.getFirstTimeInMonth().addDays(4), and so on.</li>
</ol>("Data setting formula" can also be used in other data items. For details, refer to "M227: Set to combine business data and arithmetic operations automatically")<br />
<br />
<a name='more'></a><br />
For the method to set "deadline after 7 days", in fact, it can be realized even by "Timer Intermediate Event" alone (Questetra Ver. 11.7).<br />
<br />
<div style="text-align: center;">[Event_Acceptance-Questionnaire (Expiration-v2)]</div><a href="http://4.bp.blogspot.com/-yEeGrjelky8/Wz3icUn7aYI/AAAAAAAAMWo/2lRBOzRw__MMuDt-hvQ5K_cSg-bT1vNSwCK4BGAYYCw/s1600/20180702-Event_Acceptance-Questionnaire-Expiration2-model-en-721399.png"><img alt="" border="0" height="244" id="BLOGGER_PHOTO_ID_6574660007231187330" src="https://4.bp.blogspot.com/-yEeGrjelky8/Wz3icUn7aYI/AAAAAAAAMWo/2lRBOzRw__MMuDt-hvQ5K_cSg-bT1vNSwCK4BGAYYCw/s640/20180702-Event_Acceptance-Questionnaire-Expiration2-model-en-721399.png" width="640" /></a><br />
<br />
In addition to specifying a Data Item in the timer setting, you can now specify "formula". The "expiration after 7 days" that we realized with two Step icons so far, can now be realized with one Step icon.<br />
<br />
<div style="text-align: center;"><"Wait for answer" setting screen></div><a href="http://3.bp.blogspot.com/-tBpvK_6jFzk/Wz3ib3h8fdI/AAAAAAAAMWg/DZpzF1K3Au4KXlP7nFqYYxyaN2aKNUlEQCK4BGAYYCw/s1600/20180709-Event_Acceptance-Questionnaire-Expiration2-setting-en-719078.png"><img alt="" border="0" height="508" id="BLOGGER_PHOTO_ID_6574659999421464018" src="https://3.bp.blogspot.com/-tBpvK_6jFzk/Wz3ib3h8fdI/AAAAAAAAMWg/DZpzF1K3Au4KXlP7nFqYYxyaN2aKNUlEQCK4BGAYYCw/s640/20180709-Event_Acceptance-Questionnaire-Expiration2-setting-en-719078.png" width="640" /></a><br />
<br />
Not only it is easy to set up, but to increase the visibility of the Workflow diagram with fewer Step icons is also important in the visualization of the flow of work.<br />
<br />
Reducing the number of Step icons is one of such method. It may be a good idea to boldly delete Step icons that are not being used. 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.<br />
<br />
The Workflow diagram also plays a big role in grasping the progress of Issues. Please always try to draw Workflow diagrams that are easily understandable not only for the Workflow designer him or herself but also for the person in charge of operating Tasks.<br />
<br />
<h3>Similar Models</h3><ul><li><a href="https://en.workflow-sample.net/2017/06/auto-timer-operation.html">Episode 539: A Step to be Considered as "Received" when the Time Comes (2017-06-11)</a></li>
<li><a href="https://en.workflow-sample.net/2015/06/progress-report-3.html">Steps that Skip its Processing at the Deadline (2015-06-01)</a></li>
<li><a href="https://en.workflow-sample.net/2014/11/end-timer.html">Create a Mechanism that 'Daily Report' which might have been Piled up, won't be so! (2014-11-04)</a></li>
</ul><br />
<br />
<h3><n2>Free download</n2></h3>Business Template : <a href="https://support.questetra.com/templates/20180709-event-acceptance-questionnaire-expiration2/?dmy=.qar">Event_Acceptance-Questionnaire (Expiration-v2)</a> <br />
<br />
<br />
<h3>Related Articles</h3><ul><li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259891-M203">M203 (BUSINESS FLOW) Parallel, Single Split and Multiple Split</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245512-M223">M223 (AUTO EVENT) Sleeping in the Middle</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260571-M227">M227 (AUTOMATED STEP) Auto Executing Data Binding, Arithmetic Operations</a> (Manual)</li>
</ul><br />
(<a href="https://ja.workflow-sample.net/2018/07/EventAcceptanceQuestionnaire3.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-3233540317979431842018-07-01T16:00:00.000-04:002018-07-01T16:00:14.718-04:00Episode 594: Set Expiration to Post-Event Questionnaire<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6572406417413994482" src="https://1.bp.blogspot.com/-6pyCLe72PBI/WzXg0IV1d_I/AAAAAAAAMVQ/i2afxV1xHFouMoeh8vmT6hzMFRAo9-LogCK4BGAYYCw/s640/Event_Acceptance_flow3-716519.png" width="640" /></div>
<div class="mobile-photo">
<br /></div>
In the previous article, we added a mechanism for conducting a post-event questionnaire, to a Workflow for accepting participation in events such as "small group seminars". Impressions and feedback about an event from participants obtained by answering a questionnaire, they are hints to change the next event to a better one.<br />
<br />
However, with the Workflow in the previous article, you had to "wait until the questionnaire was answered". If all the participants answered the questionnaire immediately, your work would proceed smoothly. But unfortunately, it wouldn't go that way easier. Sometimes you wouldn't answer a questionnaire. (Neither do I...)<br />
<br />
Thus, I am going to improve the Workflow by setting the expiration. If there is no answer even it comes to the expiration, the Issue is to be automatically terminated.<br />
<br />
<div style="text-align: center;">
[Event_Acceptance-Questionnaire (Expiration)]</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://4.bp.blogspot.com/-IJPKkTeOKwM/WzXlT2tnyTI/AAAAAAAAAWc/TKn6l-Dx02clmP0sWNbBk9rk8ZeDqTfeQCLcBGAs/s1600/20180702-Event_Acceptance-Questionnaire2-en.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="466" data-original-width="1215" height="244" src="https://4.bp.blogspot.com/-IJPKkTeOKwM/WzXlT2tnyTI/AAAAAAAAAWc/TKn6l-Dx02clmP0sWNbBk9rk8ZeDqTfeQCLcBGAs/s640/20180702-Event_Acceptance-Questionnaire2-en.png" width="640" /></a></div>
<br />
<a name='more'></a><br />
<br />
It is set to be closed 7 after days later the questionnaire request has been made. It would be better if it was able to set the deadline directly in the Form standby Step ("Receive Task (Form)"), but since such setting is impossible, a little ingenuity is necessary.<br />
<br />
Upon requesting for answering the questionnaire, the flow is split in two. And on one of the split flow, "Timer Intermediate Event" is arranged. The token proceeds 7 days after, and if it is answered, it advances to the "End Event". If not, it flows to the "Terminate End Event". If it goes to "Terminate End Event", the Process will be automatically terminated and the questionnaire form will become invalid.<br />
<br />
Even though the URL of the questionnaire form is made up of a character string that is hard to conjecture, it may not be desirable to remain open depending on the display content and the work content. Moreover, if its period is indefinite, the risk of being attacked is high. Considering those, it is good to set an expiration so that it will be automatically terminated.<br />
<br />
<div style="text-align: center;">
[Data Items list]</div>
<a href="http://1.bp.blogspot.com/-_hmGyAneElY/WzXg0rG_N9I/AAAAAAAAMVg/JUof0Z4DcSQNDpMcZKf6pfVQK0mBzgsCgCK4BGAYYCw/s1600/20180702-Event_Acceptance-Questionnaire2-data-en-718145.png"><img alt="" border="0" height="428" id="BLOGGER_PHOTO_ID_6572406426746959826" src="https://1.bp.blogspot.com/-_hmGyAneElY/WzXg0rG_N9I/AAAAAAAAMVg/JUof0Z4DcSQNDpMcZKf6pfVQK0mBzgsCgCK4BGAYYCw/s640/20180702-Event_Acceptance-Questionnaire2-data-en-718145.png" width="640" /></a><br />
<br />
<h3>
<n2>Free download</n2> Business Template</h3>
<a href="https://support.questetra.com/templates/questionnaire-summary/20180702-event_acceptance-questionnaire-expiration/?dmy=.qar">Event_Acceptance-Questionnaire (Expiration)</a><br />
<br />
<h3>
Similar Models</h3>
<br />
<ul>
<li><a href="https://en.workflow-sample.net/2017/06/auto-timer-operation.html">Episode 539: A Step to be Considered as "Received" when the Time Comes (2017-06-12) </a></li>
<li><a href="https://en.workflow-sample.net/2015/06/progress-report-3.html">Steps that Skip its Processing at the Deadline (2015-06-01) </a></li>
<li><a href="https://en.workflow-sample.net/2014/11/end-timer.html">Create a Mechanism that 'Daily Report' which might have been Piled up, won't be so! (2014-11-04) </a></li>
</ul>
<br /><br />
<h3>
Related articles</h3>
<br />
<ul>
<li><a href="https://support.questetra.com/en-us/developer-blog/receive-task-form-deadline/">How to Utilize Receive Task (Form) - Set a Deadline for Application Form</a></li>
</ul>
<br /><br />
<h3>
Related Manual</h3>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259891-M203">M203 (BUSINESS FLOW) Parallel, Single Split and Multiple Split</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245512-M223">M223 (AUTO EVENT) Sleeping in the Middle</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260571-M227">M227 (AUTOMATED STEP) Auto Executing Data Binding, Arithmetic Operations</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002248252-M402">M402 (BUSINESS FLOW) Setting: "Overall Stop" during Parallel Processing</a> (Manual)</li>
</ul>
<br /><ul>
</ul>
(<a href="https://ja.workflow-sample.net/2018/07/EventAcceptanceQuestionnaire2.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-58228186235399119202018-06-24T16:00:00.000-04:002018-06-24T23:46:13.985-04:00Episode 593: Questionnaire Surveillance after Event<div class="mobile-photo">
<div class="separator" style="clear: both; text-align: center;">
<img border="0" data-original-height="630" data-original-width="1200" height="336" src="https://2.bp.blogspot.com/-deEGcEUQHN4/WzBlerGQOgI/AAAAAAAAAV0/fV7NVo2UPD8vRgqayyCyOjmOFmZCCsyUACLcBGAs/s640/Event_Acceptance_flow2.png" width="640" /></div>
<br /></div>
In the previous article, I introduced a Workflow for event participation reception of such as "Seminar by a small group".<br />
It is desirable to be rid of correspondence in emails by a person in charge and to make the mechanism of reception into Workflow, also in the aspect of A: Data Management, and B: Flow Improvement.<br />
<br />
After the event has been successfully held, you would like to hear from the participants for their impressions and feedback on the event. By listening to the participant's voices and reflecting them on the next event, "Event holding work" itself can also be improved. In case the event is a seminar, it will also lead to reviewing of the contents of the seminar.<br />
<br />
Although there is a method that to prepare a Workflow for collecting "Post-event Questionnaire" and to transmit the answering URL (Form Start) to the event participants collectively, I will introduce a method that to standby for entries to the questionnaire (Form Standby) in the post-step of "Event acceptance flow", this time.<br />
<br />
<div style="text-align: center;">
[Event Acceptance flow-Questionnaire]</div>
<a href="http://2.bp.blogspot.com/-e7qwMTzKRwE/WyxuqfFa6fI/AAAAAAAAMUc/UsSBf7UFBfMtVv5QjxZfspxzHIiUemNtwCK4BGAYYCw/s1600/Event_Acceptance-Questionnaire-model-en-769123.PNG"><img alt="" border="0" height="228" id="BLOGGER_PHOTO_ID_6569747632604506610" src="https://2.bp.blogspot.com/-e7qwMTzKRwE/WyxuqfFa6fI/AAAAAAAAMUc/UsSBf7UFBfMtVv5QjxZfspxzHIiUemNtwCK4BGAYYCw/s640/Event_Acceptance-Questionnaire-model-en-769123.PNG" width="640" /></a><br />
<br />
<a name='more'></a><br />
In this Workflow definition, not only "Participation acceptance", but also "questionnaire" after the event can be conducted.<br />
<br />
For each event participant, a unique URL for answering the questionnaire will be emailed. Participants can answer the questionnaire by opening the URL described in the email.<br />
<br />
In the "Questionnaire" Step, if you set it so that "Name" and "Affiliation" at the time of acceptance are displayed, participants can be conscious as a registered questionnaire. On the other hand, in the case of this mechanism (Workflow), the person who answered it is known, even if you do not include "Name" "Affiliation" in the questionnaire item. Therefore, it is not suitable for an anonymous questionnaire.<br />
<br />
<div style="text-align: center;">
[Data Items list]</div>
<a href="http://1.bp.blogspot.com/-D-h4xuOU-pk/WyxupuZMACI/AAAAAAAAMUE/D3jZj4MS1dYu3mLlyCtUk6PmDrgPV-_2gCK4BGAYYCw/s1600/Event_Acceptance-Questionnaire-data-en-766228.PNG"><img alt="" border="0" height="410" id="BLOGGER_PHOTO_ID_6569747619534077986" src="https://1.bp.blogspot.com/-D-h4xuOU-pk/WyxupuZMACI/AAAAAAAAMUE/D3jZj4MS1dYu3mLlyCtUk6PmDrgPV-_2gCK4BGAYYCw/s640/Event_Acceptance-Questionnaire-data-en-766228.PNG" width="640" /></a><br />
<br />
<h2>
Similar Models</h2>
<br />
<ul>
<li> <a href="https://en.workflow-sample.net/2014/09/questionnaire.html">'In-house Questionnaire' Frequent in General Purpose Review Request</a> (2014-09-29)</li>
<li><a href="https://en.workflow-sample.net/2014/10/questionnaire-2.html">Data Structure of an 'In-house Questionnaire' that Gathers n Answers to One Project</a> (2014-10-06)</li>
<li><a href="https://en.workflow-sample.net/2014/02/regular-expression-check.html">Take Advantage of the Exhibition Questionnaire</a> (2014-02-10) </li>
</ul>
<br />
<n2><br /></n2>
<br />
<h2>
Related Articles</h2>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245412-M220">M220 (AUTO START) Auto Starting Triggered by Published Web Form Entry</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245532-M224">M224 (AUTO EVENT) Auto Sending of Email with Business data Inserted</a> (Manual)</li>
</ul>
<div>
<n2>Free download</n2> Business Template : <a href="https://support.questetra.com/en/templates/20180625-event-acceptance-questionnaire/?dmy=.qar">Event Acceptance flow-Questionnaire</a></div>
<div>
<a href="https://www.blogger.com/Event_Acceptance_flow-Questionnaire-en.qar"><br /></a></div>
(<a href="https://ja.workflow-sample.net/2018/06/EventAcceptanceQuestionnaire.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-37179220897610340312018-06-17T16:00:00.000-04:002018-06-21T01:19:40.782-04:00Episode 592: Event Participation Acceptance with Workflow<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6566862046050681410" src="https://1.bp.blogspot.com/-wBmEzJVJ-lE/WyIuPPfYgkI/AAAAAAAAMTA/u2nEwuJHxFI4Ar76HgTZm8O_EV_mdaZcgCK4BGAYYCw/s640/Event_Acceptance-716177.png" width="640" /></div>
<div class="mobile-photo">
<br /></div>
<div class="mobile-photo">
How do you handle acceptance of participation for events and seminars?</div>
<br />
When you assume 100, 500, 1000 applicants, you will try very hard to build an 'Automatic Processing System'.<br />
On the other hand, however, suppose if it is the scale of 10, 20, 50 people?<br />
<br />
An event acceptance for a "small seminar", for example...<br />
<br />
The quickest way is to set an Email address for accepting, and let the accepting work to be "correspondence in emails by the person in charge". That has a good aspect as well. Whatever it is for, it is very important to take action quickly.<br />
<br />
However, if it is supposed to become "an event that will be repeatedly held", you may better get out from the manner of "correspondence in emails by the person in charge" at some occasion. That is, eliminate the situation that "only the person in charge knows" about the operations, and make it (semi-automatically as much as possible) exactly to be [recorded].<br />
<br />
<ul>
<li>A. Data management</li>
<li>B. Flow improvement</li>
</ul>
<br />
Once you have made it into Workflow on the basis of the two perspectives, [taking over on replacement] of the person in charge of the acceptance becomes easier. A collaborative response will be able to be realized quickly even when [reinforcement of receptionist personnel]. And even though if it is an event of "once a year", you will not fall into the situation that 'Do you remember how we did it last year?'.<br />
<br />
<div style="text-align: center;">
[Event Acceptance flow]</div>
<a href="http://2.bp.blogspot.com/-J8gFaldaI9I/WyIuPqWXrlI/AAAAAAAAMTY/SysZMLCFGPARRCqCWO1iea1e1LRklXBZgCK4BGAYYCw/s1600/Event_Acceptance-model-en-718237.PNG"><img alt="" border="0" height="274" id="BLOGGER_PHOTO_ID_6566862053260635730" src="https://2.bp.blogspot.com/-J8gFaldaI9I/WyIuPqWXrlI/AAAAAAAAMTY/SysZMLCFGPARRCqCWO1iea1e1LRklXBZgCK4BGAYYCw/s640/Event_Acceptance-model-en-718237.PNG" width="640" /></a><br />
<br />
<a name='more'></a><br />
<br />
In this workflow definition, it is assumed to embed the "entry form" to the website.<br />
<br />
Workflow is started by the applicant's applying from the website. Inevitably, it is 'recorded automatically', and can be browsed by workers who have Data Viewing authorization at any time.<br />
<br />
The subsequent correspondence is in a general-purpose mechanism that receptionist to manually record the history of exchange circumstance, besides the transmission of "acceptance completion email" has been automated. In addition, if there is an "operation to be carried out always", it might be better to be added as a Step.<br />
<br />
<div style="text-align: center;">
[Event Acceptance flow;'1. Confirmation/Acceptance Completion Email' screen]</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://2.bp.blogspot.com/-KP7EVJETnz8/WyM0-2lLPmI/AAAAAAAAAVA/yQ1Eis_vS_U36w1qVQAH0c_EGnvHW7x2QCLcBGAs/s1600/20140324-f-en-773617.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1511" data-original-width="897" height="640" src="https://2.bp.blogspot.com/-KP7EVJETnz8/WyM0-2lLPmI/AAAAAAAAAVA/yQ1Eis_vS_U36w1qVQAH0c_EGnvHW7x2QCLcBGAs/s640/20140324-f-en-773617.png" width="378" /></a></div>
<br />
<div style="text-align: center;">
[Data Item List]</div>
<a href="http://4.bp.blogspot.com/-j6oJCa4Od_k/WyIuPc3iiuI/AAAAAAAAMTM/f8rsgerZDOU_OOirsm48hSXaPCq3pDidwCK4BGAYYCw/s1600/Event_Acceptance-data-en-717024.PNG"><img alt="" border="0" height="298" id="BLOGGER_PHOTO_ID_6566862049641663202" src="https://4.bp.blogspot.com/-j6oJCa4Od_k/WyIuPc3iiuI/AAAAAAAAMTM/f8rsgerZDOU_OOirsm48hSXaPCq3pDidwCK4BGAYYCw/s640/Event_Acceptance-data-en-717024.PNG" width="640" /></a><br />
<br />
<Similar Models><br />
<br />
<ul>
<li><a href="https://en.workflow-sample.net/2014/03/pdf-auto-generation.html">Sending Certificate of Participation for Event in PDF (Workflow Automation)</a> (2014-03-17)</li>
<li><a href="https://en.workflow-sample.net/2017/10/receipt-number.html">Episode 558: Ingeniousness in Numbering of "Reception Number" to Reduce Complainer</a> (2017-10-23)</li>
<li><a href="https://en.workflow-sample.net/2016/04/payment-confirmation.html">Episode 477: Business Process that Begins with a Request from the Outside is Worthy of Improvement</a> (2016-04-04)</li>
<li><a href="https://ja.workflow-sample.net/2018/06/Event_Acceptance.html">[Japanese Entry (和文記事)]</a> </li>
</ul>
<h3>
<n2>Free download</n2> Business Template</h3>
<ul>
<li><a href="https://support.questetra.com/templates/20180618-event-acceptance/">Event Acceptance flow (Published_Form)</a></li>
</ul>
<h2>
Related Articles</h2>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245412-M220">M220 (AUTO START) Auto Starting Triggered by Published Web Form Entry</a> (Manual)</li>
</ul>
(<a href="https://ja.workflow-sample.net/2018/06/Event_Acceptance.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-35577369647586476542018-06-10T16:00:00.000-04:002018-06-15T01:13:50.628-04:00Episode 591: Brush Up Input Screen so that Leading to Business Improvement!<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6564622616142316290" src="https://2.bp.blogspot.com/-lxfNWQcUdqc/Wxo5fQ-ogwI/AAAAAAAAMSI/-HQUorffEN8cFwyagepVyrfBq5SGpd5VgCK4BGAYYCw/s640/20180611-InputForm-Test-fi-708959.png" width="640" /></div>
<div class="mobile-photo">
<br /></div>
For a business system that is used every day, it is very important for users whether the input interface (input screen) is easy to understand and whether it is easy to use.<br />
<br />
Relating a Workflow system, I often hear people saying such as;<br />
<br />
<ul>
<li> "I don't know what to input."</li>
<li>"It could be easier if there were examples or templates."</li>
<li>"I entered all the way, but it ended up as an error."</li>
<li>"The way of input varies depending on individuals."</li>
</ul>
<br />
And when I look back at our day-to-day operations, such as "Report of hours worked", "Request for approval", "Report of order receipt", "Answer to inquiries", etc., many of the occurrences of delays and reworks are mostly caused by erroneous or inappropriate input at upstream Steps.<br />
<br />
"Improvement of work" tends to be a grandiose story such as standardization of business flow and optimal placement of resources, but as the content to be tackled becomes bigger, it takes time to get the effect. On the other hand, it can be said that "devising the input screen to reduce inputs that is erroneous and inappropriate" is a small "business improvement" that can be addressed immediately in daily work. Iterating small improvements will lead to major achievements.<br />
<br />
In this workflow sample, I would like to introduce you the devising of "input example button" on an input screen, which allows input by clicking on it.<br />
<br />
<br />
<div style="text-align: center;">
[Test flow for Input form]</div>
<a href="http://1.bp.blogspot.com/-VG1_2J_ZDX0/Wxo5fUtLeqI/AAAAAAAAMSQ/tKE4F0dJeCcf71BdeKSyHKlYq98lUNMLQCK4BGAYYCw/s1600/20170508-en-767748-709555.png"><img alt="" border="0" height="206" id="BLOGGER_PHOTO_ID_6564622617142852258" src="https://1.bp.blogspot.com/-VG1_2J_ZDX0/Wxo5fUtLeqI/AAAAAAAAMSQ/tKE4F0dJeCcf71BdeKSyHKlYq98lUNMLQCK4BGAYYCw/s640/20170508-en-767748-709555.png" width="640" /></a><br />
<br />
<br />
<div style="text-align: center;">
[Test flow for Input form: "1. Input Test" screen]</div>
<a href="http://1.bp.blogspot.com/-TP3zmN22vro/Wxo5e4rFUZI/AAAAAAAAMSA/c-nU3ACshkgupTG1CSrks9E5i8qv-DdIACK4BGAYYCw/s1600/20180611-mov-en-707166.gif"><img alt="" border="0" height="360" id="BLOGGER_PHOTO_ID_6564622609617867154" src="https://1.bp.blogspot.com/-TP3zmN22vro/Wxo5e4rFUZI/AAAAAAAAMSA/c-nU3ACshkgupTG1CSrks9E5i8qv-DdIACK4BGAYYCw/s640/20180611-mov-en-707166.gif" width="640" /></a><br />
<br />
<br />
When designing the input screen, it is basically necessary to set a "Data Item name" that is easy to understand, and to describe sentences and examples (Input hint) that explain how to input. Furthermore, by making it possible to select by option instead of typing, or by setting the initial value of data, the burden of inputting for a user is reduced and it also leads to suppression of variations in input data.<br />
<br />
In addition to these means, it is also a good idea to consider using scripts such as arranging buttons for input assistance or performing input checking or setting data to other Data Items.<br />
<br />
Even though you can set arbitrary HTML/JavaScript in [Input hint] of Questetra, in some cases it may be a trouble such as "it will destroy the layout of the whole input form". It must be set by staff members who have knowledge and experiences of HTML/JavaScript at their own risk within the range of their capability of maintenance.<br />
<br />
▼[Input Hint] Setting Example (HTML/JavaScript):"Service Item"<br />
<pre class="prettyprint linenums">E.g.: <button type="button" id="btnConsultant_1">Monthly advisory fee</button>、
<button type="button" id="btnInstruct_1">Workshop instructor fee (Diem)</button>、
<button type="button" id="btnDoc_1">Documentation fee</button>
<script type="text/javascript">
jQuery('#btnConsultant_1').on('click',function(){
jQuery('input[name="data\\[1\\].input"]').val( "Monthly advisory fee" );
});
jQuery('#btnInstruct_1').on('click',function(){
jQuery('input[name="data\\[1\\].input"]').val( "Workshop instructor fee (Diem)" );
});
jQuery('#btnDoc_1').on('click',function(){
jQuery('input[name="data\\[1\\].input"]').val( "Documentation fee" );
});
</script>
</pre>
▼[Input Hint] Setting Example (HTML/JavaScript):"Quotation price"<br />
<pre class="prettyprint linenums">E.g.: <button type="button" id="btnS_2">(15 years career) 820,000</button>、
<button type="button" id="btnA_2">(5 years career) 452,000</button>、
<button type="button" id="btnB_2">(Less than 15 years) 339,000</button>
<script type="text/javascript">
jQuery('#btnS_2').on('click',function(){
jQuery('input[name="data\\[2\\].input"]').val( "820000" );
});
jQuery('#btnA_2').on('click',function(){
jQuery('input[name="data\\[2\\].input"]').val( "452000" );
});
jQuery('#btnB_2').on('click',function(){
jQuery('input[name="data\\[2\\].input"]').val( "339000" );
});
jQuery('input[name="data\\[2\\].input"]').parent().parent().css("background-color","#FFC0CB");
</script>
</pre>
▼[Input Hint] Setting Example (HTML/JavaScript):"Reason for Leave"<br />
<pre class="prettyprint linenums">E.g.: <button type="button" id="btn1_5">Leisure and Home matter: Private</button>、
<button type="button" id="btn2_5">Local volunteer: Private (Local volunteer)</button>、
<button type="button" id="btn3_5">Got abdominal pain in the morning: Illness (abdominal pain)</button>、
<button type="button" id="btn4_5">Child's fever: Child care</button>
<script type="text/javascript">
jQuery('#btn1_5').on('click',function(){
jQuery('input[name="data\\[5\\].input"]').val( "Private" );
});
jQuery('#btn2_5').on('click',function(){
jQuery('input[name="data\\[5\\].input"]').val( "Private (Local volunteer)" );
});
jQuery('#btn3_5').on('click',function(){
jQuery('input[name="data\\[5\\].input"]').val( "Illness (abdominal pain)" );
});
jQuery('#btn4_5').on('click',function(){
jQuery('input[name="data\\[5\\].input"]').val( "Child care" );
});
</script>
</pre>
▼[Input Hint] Setting Example (HTML/JavaScript):"Approval request overview" "Budget classification"<br />
<pre class="prettyprint linenums">Frequent: <button type="button" id="btnExhibit_78">(Exhibitions within budget)</button>、
<button type="button" id="btnProcurement_78">(Unexpected procurement)</button>
<script type="text/javascript">
jQuery('#btnExhibit_78').on('click',function(){
jQuery('input[name="data\\[7\\].input"]').val( "Outsourcing related to the Cloud Expo" );
jQuery('input[name="data\\[8\\].selects"][value="1"]').prop('checked', true);
});
jQuery('#btnProcurement_78').on('click',function(){
jQuery('input[name="data\\[7\\].input"]').val( "Purchase of personal computers due to breakdown" );
jQuery('input[name="data\\[8\\].selects"][value="3"]').prop('checked', true);
});
</script>
</pre>
▼[Input Hint] Setting Example (HTML/JavaScript):"Reason of request"<br />
<pre class="prettyprint linenums"><span style='color:#ff0000;'>* Brief in Bullet</span><br>
E.g.: <button type="button" id="btnReasonA_9">(P.C. breakdown)</button>、
<button type="button" id="btnReasonB_9">(Abrupt procurement due to the increase of personnel)</button>、
</pre>
<pre class="prettyprint linenums"><script type="text/javascript">
jQuery('#btnReasonA_9').on('click',function(){
var myReason = "";
myReason += "External Monitor output is corrupted by the dropping in transportation (Dec. 2015)\n";
myReason += "Hindrance to the operation of the latest OS, past more than three years since the purchase of January 2013.\n";
myReason += "Choose a familiar conventional series machine, even though D Company is not the lowest price, but the difference is small.";
jQuery('textarea[name="data\\[9\\].input"]').val( myReason );
});
jQuery('#btnReasonB_9').on('click',function(){
var myReason = "";
myReason += "Increase 30 part-timers to correspond due to receiving order of more than assumed.\n";
myReason += "20 spare PC. Need 10 more.\n";
myReason += "(D company is the cheapest and fastest.)";
jQuery('textarea[name="data\\[9\\].input"]').val( myReason );
});
</script>
</pre>
▼[Input Hint] Setting Example (HTML/JavaScript):"Service start"<br />
<pre class="prettyprint linenums"><button type="button" id="btnThisMon_11">This month</button>、
<button type="button" id="btnNextMon_11">Next month</button>
<script type="text/javascript">
jQuery('#btnThisMon_11').on('click',function(){
var myToday = new Date();
var y = myToday.getFullYear();
var m = myToday.getMonth() + 1; // Jan: 0
if (m < 10) { m = '0' + m; }
jQuery('input[name="data\\[11\\].input"]').val( y + "-" + m );
});
jQuery('#btnNextMon_11').on('click',function(){
var myToday2 = new Date();
myToday2.setDate(1);
myToday2.setMonth(myToday2.getMonth() + 1);
var y2 = myToday2.getFullYear();
var m2 = myToday2.getMonth() + 1; // Jan: 0
if (m2 < 10) { m2 = '0' + m2; }
jQuery('input[name="data\\[11\\].input"]').val( y2 + "-" + m2 );
});
</script>
</pre>
▼[Input Hint] Setting Example (HTML/JavaScript):"Service end"<br />
<pre class="prettyprint linenums"><button type="button" id="btnOneYear_12">→1 year cintract</button>、
<button type="button" id="btnTwoYear_12">→2 years contract</button>
<script type="text/javascript">
jQuery('#btnOneYear_12').on('click',function(){
var myDateStr = jQuery('input[name="data\\[11\\].input"]').val();
var myStartMon = new Date( myDateStr + "-01");
var myEndMon = new Date();
myEndMon.setMonth( myStartMon.getMonth() + 11 );
var y = myEndMon.getFullYear();
var m = myEndMon.getMonth() + 1; // Jan: 0
if (m < 10) { m = '0' + m; }
jQuery('input[name="data\\[12\\].input"]').val( y + "-" + m );
});
jQuery('#btnTwoYear_12').on('click',function(){
var myDateStr = jQuery('input[name="data\\[11\\].input"]').val();
var myStartMon = new Date( myDateStr + "-01");
var myEndMon = new Date();
myEndMon.setMonth( myStartMon.getMonth() + 23 );
var y = myEndMon.getFullYear();
var m = myEndMon.getMonth() + 1; // Jan: 0
if (m < 10) { m = '0' + m; }
jQuery('input[name="data\\[12\\].input"]').val( y + "-" + m );
});
</script>
</pre>
<div style="text-align: center;">
[Data Item list]</div>
<div class="mobile-photo" style="text-align: center;">
<a href="http://1.bp.blogspot.com/-2CBX5QirhAE/VyHNUlunHKI/AAAAAAAAJpE/Oom_jUQFs5Upmdtx5KBuQF-vuqyqtzIEgCK4B/s1600/20160502-d-en-741466.png"><img alt="" border="0" id="BLOGGER_PHOTO_ID_6278525109139872930" src="https://1.bp.blogspot.com/-2CBX5QirhAE/VyHNUlunHKI/AAAAAAAAJpE/Oom_jUQFs5Upmdtx5KBuQF-vuqyqtzIEgCK4B/s800/20160502-d-en-741466.png" width="500" /></a></div>
<h4>
Similar Models</h4>
<ul>
<li><a href="https://en.workflow-sample.net/2016/07/input-form-2.html">Episode 490: Placing a Button for Automatic Password Generation</a> (2016-07-04)</li>
<li><a href="https://en.workflow-sample.net/2017/05/preventing-data-input-error-1.html">Episode 533: Devising to Prevent Numeric Input Errors</a> (2017-05-01)</li>
<li><a href="https://en.workflow-sample.net/2017/05/preventing-data-input-error-2.html">Episode 534: Devising to Prevent Date Input Errors</a> (2017-05-08)</li>
</ul>
<h4>
Related Articles</h4>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245252-M213">M213 (OPERATING SCREEN) Guidance Shown on Operating Screen (HTML/JavaScript)</a> (Manual)</li>
</ul>
<div>
<br /></div>
<div>
<n2>Free download</n2> Business Template : <a href="https://support.questetra.com/templates/20180611-inputform-test/?.qar">Test flow for Input form</a><span id="goog_404589390"></span><a href="https://www.blogger.com/"></a><span id="goog_404589391"></span></div>
<div>
<br /></div>
(<a href="https://ja.workflow-sample.net/2018/06/date-input-form-test.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-2063669308946769702018-06-03T16:00:00.000-04:002018-06-03T16:00:08.901-04:00Episode 590: Designation in Uneven Hierarchy, part 4<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6561628010281828466" src="https://1.bp.blogspot.com/-6kmulqrtTLE/Ww-V6Q0aAHI/AAAAAAAAMRg/ma2RyfC0D5Mx8noQp2sguOAaX1qOPqPSQCK4BGAYYCw/s640/20180604-approval-flow-4-773744.png" width="640" /></div>
Concerning "Designation in Uneven Hierarchy", we learned methods for "<a href="https://en.workflow-sample.net/2018/05/approval-flow-1.html">Absolute designation according to the job title</a>, "<a href="https://en.workflow-sample.net/2018/05/approval-flow-2.html">Relative designation according to organization hierarchy</a>, and "<a href="https://en.workflow-sample.net/2018/05/approval-flow-3.html">Methods of separating business processes, designating approver</a>".<br />
<br />
As the last of this series, I will introduce a <a href="https://en.workflow-sample.net/2016/02/approval-request.html">past article</a> that describes "Method of separating the starting position according to job position".<br />
<br />
Even though it is a similar idea to "Method of separating business processes", it addresses by separating the start position in one business process in this article. Although it is a "method of starting by boss" instead of "method of designating boss", please keep it in your memory as one of the methods of designing a Workflow App for an organization with variations in its hierarchy.<br />
<br />
<a name='more'></a><br />
<br />
<h2>
Episode 471: I won't Give an Approval to My Own Application! (by a director of a department)</h2>
An approval request written by a department director...<br />
<br />
The act that to ask authorized people for decision-making is not necessary because the director him/herself is an authority. Particularly, if the decision-making is for matters within the budget of the department. However, even so, a rule that "Must create Approval request document" is adopted in many companies. That is, they are standing on a perspective that "Intentions which have been formed in the organization will be preserved in documents as records". Also, they are assuming efficiency in corresponding to audit.<br />
<br />
Yet, it indeed is cumbersome that "to make request, and then approve it by oneself" on a Workflow system.<br />
<br />
The following Workflow is a modified version of "<a href="http://en.workflow-sample.net/2015/12/starter-templates-2016-planning-approval.html">Episode 462: Planning - Approval (Starter Template)</a>", which has been compiled in <a href="http://www.questetra.com/blog/cat-ambitions/starter-template-2016/">Basic Business operations 2016 edition</a>. Users who have "Managers role" are able to submit their approval requests via a flow which does not pass through "2. Approval".<br />
<br />
<div style="text-align: center;">
[Approval Request] </div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://1.bp.blogspot.com/-IROpULbm2o4/WxDX62oI2sI/AAAAAAAAAUE/dAS8pASQ1bUERxwLVvmX8ciCFmBmNz9ggCLcBGAs/s1600/20160222-en-773045.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1016" data-original-width="1091" height="595" src="https://1.bp.blogspot.com/-IROpULbm2o4/WxDX62oI2sI/AAAAAAAAAUE/dAS8pASQ1bUERxwLVvmX8ciCFmBmNz9ggCLcBGAs/s640/20160222-en-773045.png" width="640" /></a></div>
<br />
As you see in comparison between the Business Flow Diagram before the modification (below), this Diagram has been added a Step of "2x. Request from the Director" at the top. That means a User who has "Director role" is able to Start this Workflow from "2x. Request from the Director". There is no "Double effort" on the flow.<br />
<br />
<div style="text-align: center;">
Planning-Approval flow in "Episode 462: Planning - Approval"</div>
<a href="http://1.bp.blogspot.com/-kI8kruOHc78/Ww-V5OaD1cI/AAAAAAAAMQw/t_Z7DH3Zv2knTwqSDaNX02RGH3-yr44owCK4BGAYYCw/s1600/20180604-Approval-Request_model_en-768244.png"><img alt="" border="0" height="512" id="BLOGGER_PHOTO_ID_6561627992454583746" src="https://1.bp.blogspot.com/-kI8kruOHc78/Ww-V5OaD1cI/AAAAAAAAMQw/t_Z7DH3Zv2knTwqSDaNX02RGH3-yr44owCK4BGAYYCw/s640/20180604-Approval-Request_model_en-768244.png" width="640" /></a><br />
Incidentally, (it is obvious as well,) the request will automatically go to "3. Approval by Officers" despite it is a from a director, if "External payment of more than 1 million JPY" occurred. That is if the officer made a judgment of "disapproval", the decision itself becomes invalid.<br />
<br />
'Mmm, well then, divide it into less than 1 million...' Such an idea seems "kind an ulterior motive", but it probably cannot be helped because that is the rule.<br />
<br />
<div style="text-align: center;">
[Approval Request:"2x. Request from the Director" screen] </div>
<div style="text-align: center;">
<a href="http://1.bp.blogspot.com/-pc9uxEUp7cU/Ww-V5VHajEI/AAAAAAAAMRA/VE4j7lYjMRQmh8vPcccPWDLm2c7Rq_dwwCK4BGAYYCw/s1600/20180604-Approval-Request_op_en-769557.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6561627994255428674" src="https://1.bp.blogspot.com/-pc9uxEUp7cU/Ww-V5VHajEI/AAAAAAAAMRA/VE4j7lYjMRQmh8vPcccPWDLm2c7Rq_dwwCK4BGAYYCw/s640/20180604-Approval-Request_op_en-769557.png" width="344" /></a></div>
<br />
<div style="text-align: center;">
[Sample of auto-generated PDF] </div>
<div style="text-align: center;">
<a href="http://2.bp.blogspot.com/-BRUVltyxBzM/Ww-V5_R94dI/AAAAAAAAMRM/_OUoevT2r3MZ7NuIl4CJuQKHSBXjTut4gCK4BGAYYCw/s1600/20180604-Approval-Request_pdf_en-770870.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6561628005573976530" src="https://2.bp.blogspot.com/-BRUVltyxBzM/Ww-V5_R94dI/AAAAAAAAMRM/_OUoevT2r3MZ7NuIl4CJuQKHSBXjTut4gCK4BGAYYCw/s640/20180604-Approval-Request_pdf_en-770870.png" width="452" /></a></div>
<div style="text-align: center;">
[Data Items list]</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://2.bp.blogspot.com/-0nNu8k2nn_8/WxDZGKtzhQI/AAAAAAAAAUQ/1nMrUqgBcecmTKNNIcfH_ZnOsg8PH2KhgCLcBGAs/s1600/20160222-d1-en-787517.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="813" data-original-width="1058" height="491" src="https://2.bp.blogspot.com/-0nNu8k2nn_8/WxDZGKtzhQI/AAAAAAAAAUQ/1nMrUqgBcecmTKNNIcfH_ZnOsg8PH2KhgCLcBGAs/s640/20160222-d1-en-787517.png" width="640" /></a></div>
<br />
<Similar Models><br />
<ul>
<li><a href="https://en.workflow-sample.net/2015/12/starter-templates-2016-planning-approval.html">Episode 462: Planning - Approval (Starter Template)</a> (2015-12-21)</li>
<li><a href="https://en.workflow-sample.net/2018/05/approval-flow-1.html">Episode 587: Designation in Uneven Hierarchy, part 1</a> (2018-05-14)</li>
<li><a href="https://en.workflow-sample.net/2018/05/approval-flow-2.html">Episode 588: Designation in Uneven Hierarchy, part 2</a> (2018-05-21)</li>
<li><a href="https://en.workflow-sample.net/2018/05/approval-flow-3.html">Episode 589: Designation in Uneven Hierarchy, part 3</a> (2018-05-28)</li>
<li><br /></li>
</ul>
<n2>Free download</n2> Business Template : <a href="https://questetra.github.io/app-templates/en/20160222-Approval-Request-en.qar">Approval Request</a><br />
<br />
<h2>
Related Articles</h2>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245032-M201">M201 (DEFINITION GENERAL) Defining Business Process, Running on Workflow</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260111-M207">M207 (DATA ITEM) Initial Value of Data Items Set at the Start</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260571-M227">M227 (AUTOMATED STEP) Auto Executing Data Binding, Arithmetic Operations</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245612-M228">M228 (AUTOMATED STEP) Auto Generating PDF File with Business data Inserted</a> (Manual)</li>
</ul>
(<a href="https://ja.workflow-sample.net/2018/06/approval-flow-4.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-90350957426594172722018-05-27T16:00:00.000-04:002018-05-27T16:00:03.103-04:00Episode 589: Designation in Uneven Hierarchy, part 3<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6558722414899313218" src="https://4.bp.blogspot.com/-oS4fvFbIKRM/WwVDSWh3OkI/AAAAAAAAMPQ/xlCaZQXRMPkctNEKWv0Io8Cuzn8EiYpEACK4BGAYYCw/s640/20180521-approval-flow-3-760733.png" width="640" /></div>
<div class="mobile-photo">
Regarding designation within an organization in which its hierarchy is uneven, we studied "method of absolute specification by job title" in Part 1, and "method of relative designation according to organization hierarchy" in Part 2.</div>
<br />
Both methods have advantages and disadvantages, and approver/decision-makers are needed to be careful during operation. After all, in the case of "an organization with unevenness in depth", it is difficult to simply describe business rules.<br />
<br />
The easy-to-use and easy-to-operate Workflow (setting method) will also vary depending on the size of the organization or proficiency to business rules/system of the organization members, and so on. Although we will introduce two more Workflows this time, please consider and choose "which description method is easy to operate without misunderstanding" according to the actual situation of each company including those introduced in the past articles.<br />
<br />
One way is to separate the Workflows according to the requester.<br />
In other words, if the approval route differs depending on the job title of who made a request, it may be good to separate into different Workflows.<br />
<br />
<div style="text-align: center;">
[Approval flow (Separate the request of the Manager)]</div>
<a href="http://3.bp.blogspot.com/-nd6TNoiiBrQ/WwVDRzv8JnI/AAAAAAAAMPI/bwbZ8OgcOls2Ow2qeq2u5vUL1lA4GI85gCK4BGAYYCw/s1600/Approval-separate-the-request-of-the-Manager-model-en-759595.png"><img alt="" border="0" height="198" id="BLOGGER_PHOTO_ID_6558722405563115122" src="https://3.bp.blogspot.com/-nd6TNoiiBrQ/WwVDRzv8JnI/AAAAAAAAMPI/bwbZ8OgcOls2Ow2qeq2u5vUL1lA4GI85gCK4BGAYYCw/s640/Approval-separate-the-request-of-the-Manager-model-en-759595.png" width="640" /></a><br />
<br />
<a name='more'></a><br />
In [Approval flow (absolute representation 2)] or [Approval flow (relative representation)], the settings are a little complicated for needing Splitting so that flows of different hierarchy to be realized in one Workflow.<br />
<br />
Even though there are more objects to manage, there is the merit that you can design each Workflow simple by separating the workflow.<br />
<br />
<div style="text-align: center;">
[Approval flow (Designate Approver/Decision-maker)]</div>
<a href="http://2.bp.blogspot.com/-AnTyBEyPzPA/WwVDSUWpl2I/AAAAAAAAMPc/q4d9hfxbe4QMXGIMJUM6Bn-WJU-x6OqLACK4BGAYYCw/s1600/Approval-Designate-Approver-Decision-maker-en-761805.png"><img alt="" border="0" height="282" id="BLOGGER_PHOTO_ID_6558722414315411298" src="https://2.bp.blogspot.com/-AnTyBEyPzPA/WwVDSUWpl2I/AAAAAAAAMPc/q4d9hfxbe4QMXGIMJUM6Bn-WJU-x6OqLACK4BGAYYCw/s640/Approval-Designate-Approver-Decision-maker-en-761805.png" width="640" /></a><br />
<br />
Another way is to designate the approver and the decision-maker at the time of making a request.<br />
It is a simple method that is easy-to-understand and capable of responding to any cases since the person to handle is to be directly designated. If "Approver" is not designated, "2. Approval" process will be skipped automatically.<br />
<br />
Meanwhile, since the designation of the person in charge is entrusted to the requester him/herself, it must be noted the possibilities that the case does not go to the "approver" or to the "decision-maker" as expected, for reasons such as the requester may not know the business rule well or if he/she may designate incorrectly.<br />
<br />
<br />
<div style="text-align: center;">
[Approval flow (Designate Approver/Decision-maker):"1. Request for approval" screen]</div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-XkXs2KWn-J8/WwVDS9b0qFI/AAAAAAAAMPo/PmVLjy484EMPoVICT8AfPpI8Hw9pRZTdACK4BGAYYCw/s1600/20180528-2-op-en-762895.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6558722425342961746" src="https://3.bp.blogspot.com/-XkXs2KWn-J8/WwVDS9b0qFI/AAAAAAAAMPo/PmVLjy484EMPoVICT8AfPpI8Hw9pRZTdACK4BGAYYCw/s640/20180528-2-op-en-762895.png" width="400" /></a></div>
<br />
<h3>
Download</h3>
<br />
<ul>
<li>Business Template: <a href="https://questetra.github.io/app-templates/en/20180528-Approval-separate_the_request_of_the_manager-en.qar">Approval flow (Separate the request of the Manager)</a></li>
<li>Business Template: <a href="https://questetra.github.io/app-templates/en/20180528-Approval-designate_approver_decision_maker-en.qar,">Approval flow (Designate Approver/Decision-maker)</a></li>
</ul>
<br />
<h3>
Similar Models</h3>
<br />
<ul>
<li><a href="https://en.workflow-sample.net/2018/05/approval-flow-1.html">Episode 587: Designation in Uneven Hierarchy, part 1</a> (2018-05-14) </li>
<li><a href="https://en.workflow-sample.net/2018/05/approval-flow-2.html">Episode 588: Designation in Uneven Hierarchy, part 2</a> (2018-03-21) </li>
<li><a href="https://en.workflow-sample.net/2018/03/general-work-request.html">Episode 577: Work Request Flow is the Basic of Workflow</a> (2018-03-05) </li>
</ul>
<br />
<h2>
Related Articles</h2>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260191-M209">M209 (ALLOCATION) Nomination by Organization and by Role</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260211-M210">M210 (ALLOCATION) Designation of Downstream Operator in Upstream Step</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260571-M227">M227 (AUTOMATED STEP) Auto Executing Data Binding, Arithmetic Operations</a> (Manual)</li>
</ul>
(<a href="https://ja.workflow-sample.net/2018/05/approval-flow-3.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-26570885331509123692018-05-20T16:00:00.000-04:002018-05-20T16:00:09.230-04:00Episode 588: Designation in Uneven Hierarchy, part 2<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6556745409567421778" src="https://2.bp.blogspot.com/-5UP4coaG_CA/Wv49NfvwdVI/AAAAAAAAMOs/-rWJWRfs9ToHUp9CyU2uJ3tLw7rUABSkQCK4BGAYYCw/s640/20180521-approval-flow-2-752915.png" width="640" /></div>
Continuing from the last week, let's study about "Operator setting".<br />
<br />
In the article of "<a href="https://en.workflow-sample.net/2018/05/approval-flow-1.html">Episode 587: Designation in Uneven Hierarchy, part 1</a>", I introduced you a method of two-step approval which is to obtain an approval from "superior" then obtain from the "superior's superior". It is a form of approval flow that is common even for other than decision-making. This time, I will introduce a different way of writing about the previous Workflow diagram.<br />
<br />
In the following Workflow diagram, the second Swimlane is set to "superior of the applicant" (relative designation), instead of "manager" (absolute designation by position).<br />
By setting like this, "2. Approval/Decision" task will be assigned to the manager of the organization to which the applicant belongs. That is, if a "member" among "two directors, ten managers, and fifty members" makes a request then a "manager" approves on it, and if "manager" makes, "director" approves it.<br />
<br />
<div style="text-align: center;">
[Approval flow (relative representation)]</div>
<a href="http://2.bp.blogspot.com/-Q5edaGC6BXY/Wv49L6biz8I/AAAAAAAAMOM/FqZdVOfzNsERLSHrX2YXsXlVOh8t0vCiQCK4BGAYYCw/s1600/20180521-approval-flow-model-1-en-746889.png"><img alt="" border="0" height="278" id="BLOGGER_PHOTO_ID_6556745382370660290" src="https://2.bp.blogspot.com/-Q5edaGC6BXY/Wv49L6biz8I/AAAAAAAAMOM/FqZdVOfzNsERLSHrX2YXsXlVOh8t0vCiQCK4BGAYYCw/s640/20180521-approval-flow-model-1-en-746889.png" width="640" /></a><br />
<br />
<a name='more'></a><br />
<div style="text-align: center;">
[Approval flow (relative representation): "1. Request for Approval" screen]</div>
<div style="text-align: center;">
<a href="http://2.bp.blogspot.com/-jZbQXQFGcdY/Wv49MPlt6AI/AAAAAAAAMOU/zWq7bPuxt5YwP2NLrzTW-cgKE9wxiYOmACK4BGAYYCw/s1600/20180521-approval-flow-op-1-en-748561.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6556745388050475010" src="https://2.bp.blogspot.com/-jZbQXQFGcdY/Wv49MPlt6AI/AAAAAAAAMOU/zWq7bPuxt5YwP2NLrzTW-cgKE9wxiYOmACK4BGAYYCw/s640/20180521-approval-flow-op-1-en-748561.png" width="464" /></a></div>
<br />
In the Workflow diagram introduced in the last article, when a person at the position of "manager" makes a request at "1. Request for Approval", it is necessary to continuously handle "1. Request for Approval" and "2. Manager's Approval" by him/herself. Whereas, in this Workflow diagram, it goes to director's decision by only making a request.<br />
<br />
<div style="text-align: center;">
[Approval flow (absolute representation 1)]</div>
<div style="text-align: center;">
<a href="http://4.bp.blogspot.com/-aoytHD_ESEo/Wv49MZ0-OsI/AAAAAAAAMOc/3x8-lYF2wYYwmmg_j-kuF05KP4YFlr4uwCK4BGAYYCw/s1600/20180521-approval-flow-model-2-en-749858.png"><img alt="" border="0" height="264" id="BLOGGER_PHOTO_ID_6556745390798813890" src="https://4.bp.blogspot.com/-aoytHD_ESEo/Wv49MZ0-OsI/AAAAAAAAMOc/3x8-lYF2wYYwmmg_j-kuF05KP4YFlr4uwCK4BGAYYCw/s640/20180521-approval-flow-model-2-en-749858.png" width="640" /></a></div>
<br />
However, in order to realize such a rule, "Managers" must be registered as both "team manager" and "member of the team" in the organizational assignment setting. By doing so, it becomes an operation for a "manager" "to get an approval from his/her superior as a member of the department" at the time of making a request. Incidentally, as for the Directors, they have to handle Task "2. Approval/Decision" in addition to "3. Director's Approval". However, there is no need to send to "3. Director's Approval" the Task which has processed at Task "2. Approval/Decision".<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://3.bp.blogspot.com/-u6LzHlmIMX4/Wv5CgFV26DI/AAAAAAAAATU/Haxmc2pxcBsvN-HLeefpA-2X19NuXhAdgCLcBGAs/s1600/Untitled.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="907" data-original-width="756" height="640" src="https://3.bp.blogspot.com/-u6LzHlmIMX4/Wv5CgFV26DI/AAAAAAAAATU/Haxmc2pxcBsvN-HLeefpA-2X19NuXhAdgCLcBGAs/s640/Untitled.png" width="532" /></a></div>
<br />
'Now, this will make the Directors confused...'<br />
After all, for the "Organization with a variation in depth," their Business rule cannot be described simply anyhow. In fact, the statement of Regulations itself, it is inevitable to describe the exception that "as a general rule, with the approval by Manager, Director will make the final decision". In addition, a variety of ways of drawing Workflow diagram can be considered as well as one in the last article (absolute representation 1) or the above (relative representation). Each company needs to consider and select "which description is easy to operate without misunderstanding" in accordance with the actual situation of their own.<br />
<br />
<div style="text-align: center;">
[Approval flow (absolute representation 2)]</div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-K5_FxmbphCA/Wv49M7ST4AI/AAAAAAAAMOk/P-DHQiqUhGsHxJTs6OXe1dYs3urRGhCXwCK4BGAYYCw/s1600/20180521-approval-flow-model-3-en-751382.png"><img alt="" border="0" height="272" id="BLOGGER_PHOTO_ID_6556745399780237314" src="https://3.bp.blogspot.com/-K5_FxmbphCA/Wv49M7ST4AI/AAAAAAAAMOk/P-DHQiqUhGsHxJTs6OXe1dYs3urRGhCXwCK4BGAYYCw/s640/20180521-approval-flow-model-3-en-751382.png" width="640" /></a></div>
<h3>
Similar Models</h3>
<br />
<ul>
<li><a href="https://en.workflow-sample.net/2012/01/organization-and-role-important-to.html">"Organization" and "Role", Important to Decision Making Workflow</a> (2012-01-23)</li>
<li><a href="https://en.workflow-sample.net/2013/02/ringi-proxy.html">Ringi Workflow, How to Design 'Proxy Approval'</a> (2013-02-12)</li>
<li><a href="https://en.workflow-sample.net/2016/02/approval-request.html">Episode 471: I won't Give an Approval to My Own Application! (by a director of a department)</a> (2016-02-22)</li>
<li><br /></li>
</ul>
<h3>
<n2>Free download</n2> Business Template</h3>
<br />
<br />
<ul>
<li><a href="https://questetra.github.io/app-templates/en/20180521-Approval-relative-en.qar">Approval flow (relative representation)</a><span id="goog_1379709823"></span><a href="https://www.blogger.com/"></a><span id="goog_1379709824"></span></li>
<li><a href="https://questetra.github.io/app-templates/en/20180521-Approval-absolute2-en.qar">Approval flow (absolute representation 2)</a></li>
</ul>
<br />
<h2>
Related Articles</h2>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260191-M209">M209 (ALLOCATION) Nomination by Organization and by Role</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259891-M203">M203 (BUSINESS FLOW) Parallel, Single Split and Multiple Split</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260571-M227">M227 (AUTOMATED STEP) Auto Executing Data Binding, Arithmetic Operations</a> (Manual)</li>
</ul>
(<a href="https://ja.workflow-sample.net/2018/05/approval-flow-2.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-78500510143680811842018-05-13T16:00:00.000-04:002018-05-24T22:06:40.816-04:00Episode 587: Designation in Uneven Hierarchy, part 1<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6554268374991937282" src="https://4.bp.blogspot.com/-hWGhBbLct3Q/WvVwXG34nwI/AAAAAAAAMMc/Rl0z0TbXDukV2A9ns8FRtHlP-smQq9lrACK4BGAYYCw/s640/20180514-approval-flow-1-724296.png" width="640" /></div>
<div class="mobile-photo">
<br /></div>
Let's study about "Operator setting" from popular articles of the past.<br />
To specify a "superior" is comparably difficult among settings of a Workflow since there are several ways to do and also it depends on the organization structure. It is better to know various ways of thinking at first.<br />
<br />
One President, two (executive) Directors, four managers, and twelve employees.<br />
Suppose that 4 of the "12 employees" are assigned to "directly under the Directors". More specifically,<br />
<br />
<ul>
<li>2 people are directly assigned respectively to the Departments where each of two directors supervises.</li>
<li>2 people are assigned respectively to the Units where each of 4 managers supervises.</li>
</ul>
<br />
Every "Units" are belonging to either of the "Departments", of course. Specifically, It is a case of where the sales manager himself directly directs five sales staff members besides Units under the umbrella of the sales department. And while there are many Units under the affiliation of the manufacturing department, the manufacturing department manager himself is directly supervising five people as quality control staff.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://2.bp.blogspot.com/-GvOgR3W_MIc/WvV26ebFUDI/AAAAAAAAARM/VCE1m74EAScllj4r81m9QXTfUoKm4Y3VQCLcBGAs/s1600/20180514-Approval_1-fig1-en.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="540" data-original-width="1100" height="314" src="https://2.bp.blogspot.com/-GvOgR3W_MIc/WvV26ebFUDI/AAAAAAAAARM/VCE1m74EAScllj4r81m9QXTfUoKm4Y3VQCLcBGAs/s640/20180514-Approval_1-fig1-en.png" width="640" /></a></div>
<br />
The characteristic of this organizational structure is that there is "variation in depth". It is a common story.<br />
<br />
Now, in the case of such "organization having variations in depth", what kind of business flow diagram should be to express the path of escalation in the approval flow? Let's consider how to write according to international standard notation BPMN. The point where to be controversial is how to draw an in-house rule that is "In principle, after the manager approval, the director will make a decision". That is, those five people in each department in this organization have no Manager.<br />
<br />
<br />
<div style="text-align: center;">
[Approval flow (absolute representation 1)]</div>
<a href="http://3.bp.blogspot.com/-UbeXaEtvu5c/WvVwWN6jL5I/AAAAAAAAML0/xiTXGMVFk5IulG9EIJp3YBRMvevVspxpwCK4BGAYYCw/s1600/20180514-approval-model-en-720136.PNG"><img alt="" border="0" height="282" id="BLOGGER_PHOTO_ID_6554268359702294418" src="https://3.bp.blogspot.com/-UbeXaEtvu5c/WvVwWN6jL5I/AAAAAAAAML0/xiTXGMVFk5IulG9EIJp3YBRMvevVspxpwCK4BGAYYCw/s640/20180514-approval-model-en-720136.PNG" width="640" /></a><br />
<br />
<a name='more'></a><br />
The simplest way is to consider that "The director is concurrently conferring manager".<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://4.bp.blogspot.com/-HJJtPxwx1lg/WvV3BFUhcsI/AAAAAAAAARU/lRstfG6sZ84Y0W5pEdvvwSx2dNFbNXDiwCLcBGAs/s1600/20180514-Approval_1-fig2-en.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="448" data-original-width="812" height="352" src="https://4.bp.blogspot.com/-HJJtPxwx1lg/WvV3BFUhcsI/AAAAAAAAARU/lRstfG6sZ84Y0W5pEdvvwSx2dNFbNXDiwCLcBGAs/s640/20180514-Approval_1-fig2-en.png" width="640" /></a></div>
<br />
In other words, we interpret "five sales staffs members directed by the sales director directly" as a "Sales clerk unit". It can be said that you treat it as if there is no variation of the depth in the organizational hierarchy.<br />
<br />
In this case, all requests will follow the flow of "1. Request for Approval" → "2. Manager's Approval" → "3. Director's Decision". Even though it may not be a so big trouble, if this BPMN is systematized as it is, it will be the specification which the director must handle the Task "2. approval" and "3. decision" in a sequence.<br />
<br />
Incidentally, if this idea is applied mutatis mutandis, "cases where a manager wants to make a request" can also be considered simply. That is, a manager would "1. Make request as a member", and "2. Approve as a manager", then ask the director for "3. Decision".<br />
<br />
By the way, "managers" is not an "organization" despite "sales department" is an "organization". That is, a group of "managers" is to be defined in "Role". Speaking on this Workflow diagram, all members will get an approval by "manager" in "organization to which you belong" or "superior organization".<br />
<br />
Next week, I will show you how to write a business flow diagram using relative relation. You will be able to reduce the number of Steps by eliminating "successive processing".<br />
<br />
<div style="text-align: center;">
[Data Items list]</div>
<a href="http://4.bp.blogspot.com/-CpkHGcNhF3w/WvVwWeJHALI/AAAAAAAAMMA/Y886SvMdldsFo7dRawSq66VYlm5KCpRnwCK4BGAYYCw/s1600/20180514-approval-data-en-721478.PNG"><img alt="" border="0" height="366" id="BLOGGER_PHOTO_ID_6554268364058329266" src="https://4.bp.blogspot.com/-CpkHGcNhF3w/WvVwWeJHALI/AAAAAAAAMMA/Y886SvMdldsFo7dRawSq66VYlm5KCpRnwCK4BGAYYCw/s640/20180514-approval-data-en-721478.PNG" width="640" /></a><br />
<br />
[Download]<br />
<ul>
<li>Business Template: <a href="https://questetra.github.io/app-templates/en/20180514-Approval_1-en.qar">Approval flow (absolute representation 1)</a></li>
</ul>
<br />
<Similar Models><br />
<ul>
<li><a href="https://https//en.workflow-sample.net/2012/01/organization-and-role-important-to.html">"Organization" and "Role", Important to Decision Making Workflow</a> (2012-01-23)</li>
<li><a href="https://en.workflow-sample.net/2013/02/ringi-proxy.html">Ringi Workflow, How to Design 'Proxy Approval' </a> (2013-02-12)</li>
<li><a href="https://en.workflow-sample.net/2016/02/approval-request.html">Episode 471: I won't Give an Approval to My Own Application! (by a director of a department)</a> (2016-02-22)</li>
</ul>
<h2>
Related Articles</h2>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260191-M209">M209 (ALLOCATION) Nomination by Organization and by Role</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259891-M203">M203 (BUSINESS FLOW) Parallel, Single Split and Multiple Split</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260571-M227">M227 (AUTOMATED STEP) Auto Executing Data Binding, Arithmetic Operations</a> (Manual)</li>
</ul>
(<a href="https://ja.workflow-sample.net/2018/05/approval-flow-1.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-67949166544338155552018-05-06T16:00:00.000-04:002018-05-23T03:41:33.949-04:00Episode 586: Let's Draw Workflow Diagram in BPMN! (sequel)<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6550843819348097586" src="https://4.bp.blogspot.com/-8n7sp2pGWhQ/WulFvu9OejI/AAAAAAAAMK4/85CUh8flY4wwDcb9OMqll52mqaqjCI5dgCK4BGAYYCw/s640/bpmn-introduction-781839.png" width="640" /></div>
Continuing from <a href="https://en.workflow-sample.net/2018/05/bpmn-introduction.html">last week</a>, I will introduce the past articles of "Workflow Sample" concerning the method of Workflow definition using BPMN (Business Process Model and Notation).<br />
<br />
BPMN stands for "Model" and "Notation". The Workflow definition written in BPMN can be run as Workflow system on a BPM system. Would you like to learn BPMN and try systemizing your work?<br />
<br />
For information on how to write BPMN, please also refer to <a href="https://www.questetra.com/features/modeling/bpmn-introduction/">BPMN Introduction</a>.<br />
<br />
<br />
<a name='more'></a><br />
5) <a href="https://en.workflow-sample.net/2011/05/eternal-looping.html">Eternal Looping</a><br />
<br />
In a Workflow definition, you can express various loop structures. However, there are some loop structures that cause errors, so be careful. However, there are some loop structures that cause errors, so please be aware of them.<br />
<br />
<div style="text-align: center;">
[BPMN sample-Error loop]</div>
<a href="http://1.bp.blogspot.com/-yEukeq0Jr6w/WulFvL_NvxI/AAAAAAAAMKg/81evbc2VUp0m5Cy93quR-qYO2pCxcSWGQCK4BGAYYCw/s1600/20110501-2-En-780064.png"><img alt="" border="0" height="196" id="BLOGGER_PHOTO_ID_6550843809961197330" src="https://1.bp.blogspot.com/-yEukeq0Jr6w/WulFvL_NvxI/AAAAAAAAMKg/81evbc2VUp0m5Cy93quR-qYO2pCxcSWGQCK4BGAYYCw/s640/20110501-2-En-780064.png" width="640" /></a><br />
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259951-M204">M204 (BUSINESS FLOW) Looping Structure</a> (Manual)</li>
</ul>
<br />
<br />
6) <a href="https://en.workflow-sample.net/2011/05/never-use-your-own-rules-when-designing.html">Never Use Your Own Rules When Designing Workflow Diagrams</a><br />
<br />
Learn how to write about "interrupting" of processing when multiple people are processing at the same time in parallel. In BPMN, it is defined as "Terminate End Event".<br />
<br />
<div style="text-align: center;">
[BPMN sample-Single Terminate]</div>
<div style="text-align: center;">
<a href="http://4.bp.blogspot.com/-q55WXEdOu_Y/WulFvVf7MDI/AAAAAAAAMKo/TegkAw-4lcYOMMwN-phxRsvMmZpQOzTMwCK4BGAYYCw/s1600/20110515-1-en-781040.png"><img alt="" border="0" height="254" id="BLOGGER_PHOTO_ID_6550843812514312242" src="https://4.bp.blogspot.com/-q55WXEdOu_Y/WulFvVf7MDI/AAAAAAAAMKo/TegkAw-4lcYOMMwN-phxRsvMmZpQOzTMwCK4BGAYYCw/s640/20110515-1-en-781040.png" width="640" /></a></div>
<br />
<br />
7) <a href="https://en.workflow-sample.net/2011/05/same-results-different-starts.html">Same Results, Different Starts</a><br />
<br />
A Workflow can be started by various kinds of triggers. Not only a person starts one but also methods to automatically start with a timer, etc. is assumed.<br />
<br />
<div style="text-align: center;">
[BPMN sample-Varied Multiple Start]</div>
<a href="http://2.bp.blogspot.com/-pZ8RYoHQyDk/WulFu8YnQpI/AAAAAAAAMKY/dLUV0Ci1HQc56PmuwCEQPK6JLn5CRCr6ACK4BGAYYCw/s1600/20110522-1-en-779099.png"><img alt="" border="0" height="256" id="BLOGGER_PHOTO_ID_6550843805772759698" src="https://2.bp.blogspot.com/-pZ8RYoHQyDk/WulFu8YnQpI/AAAAAAAAMKY/dLUV0Ci1HQc56PmuwCEQPK6JLn5CRCr6ACK4BGAYYCw/s640/20110522-1-en-779099.png" width="640" /></a><br />
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245312-M217">M217 (AUTO START) Auto Starting at the Time You Fix</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260431-M218">M218 (AUTO START) Auto Starting Triggered by Incoming Email</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245412-M220">M220 (AUTO START) Auto Starting Triggered by Published Web Form Entry</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245432-M221">M221 (AUTO START) Auto Starting Triggered by HTTP Request</a> (Manual)</li>
</ul>
<br />
<hr />
<h2>
Basics of BPMN, how to model in Questetra</h2>
<ul>
<li><a href="https://www.questetra.com/ja/features/modeling/bpmn-introduction/">BPMN Introduction</a></li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245032-M201">M201 (DEFINITION GENERAL) Defining Business Process, Running on Workflow</a> (Manual)</li>
</ul>
<div>
<br /></div>
(<a href="https://ja.workflow-sample.net/2018/05/bpmn-introduction2.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-62094940621787880592018-05-01T10:00:00.000-04:002018-05-23T03:41:13.941-04:00Episode 585: Let's Draw Workflow Diagram in BPMN! (prequel)<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6549055921336638130" src="https://2.bp.blogspot.com/-sMbbrNSYbrM/WuLrqX1wWrI/AAAAAAAAMBU/7WEtC_iurA08bYT7GLq6Rerfe1HtJh3YwCK4BGAYYCw/s640/20180501-BpmnIntroduction-705059.png" width="640" /></div>
<div class="mobile-photo">
<br /></div>
<div class="mobile-photo">
In this blog, "Workflow Sample", we introduce you various Workflow definitions of businesses. Since a Workflow definition is drawn using BPMN (Business Process Model and Notation), so it is not only the flow of the business to comprehensible at a glance but also sharing the contents of the business to be easy.</div>
<br />
We are going into <a href="https://en.wikipedia.org/wiki/Golden_Week_(Japan)" target="_blank">Golden Week</a>, so I will re-introduce the articles of the past concerning "how to draw BPMN" for the next two weeks. I hope you take those as an opportunity to learn about BPMN which is a notation system for Workflow diagram and how to draw with them.<br />
<a name='more'></a><br />
1) <a href="https://en.workflow-sample.net/2011/04/split-conditions-are-basic-concept-in.html" target="_blank">Split Conditions are a Basic Concept in BPMN</a><br />
<br />
<br />
A lesson for how to "Split" a flow of business. Among three types of splitting, "AND split (parallel split)" which goes to "all" and "XOR split (exclusive split)" which goes to "one of them" are explained.<br />
<br />
<div style="text-align: center;">
[BPMN sample-XOR split]</div>
<a href="http://1.bp.blogspot.com/-5tGpFTDvl24/WuLrrwA9hiI/AAAAAAAAMCU/8cOZ2kQ0cj4VTvW66iBEjO1q3izUvYwcACK4BGAYYCw/s1600/BPMN-Sample_XOR-Split-711804.png"><img alt="" border="0" height="342" id="BLOGGER_PHOTO_ID_6549055945005958690" src="https://1.bp.blogspot.com/-5tGpFTDvl24/WuLrrwA9hiI/AAAAAAAAMCU/8cOZ2kQ0cj4VTvW66iBEjO1q3izUvYwcACK4BGAYYCw/s640/BPMN-Sample_XOR-Split-711804.png" width="640" /></a><br />
<br />
<div style="text-align: center;">
[BPMN sample-AND split]</div>
<a href="http://3.bp.blogspot.com/-ir0u3LbsJpI/WuLrqmgIUTI/AAAAAAAAMBg/2gIT6YtlP9Q81DzIThG5wW0NLsj00pk6gCK4BGAYYCw/s1600/BPMN-Sample_AND-Split-706456.png"><img alt="" border="0" height="340" id="BLOGGER_PHOTO_ID_6549055925272465714" src="https://3.bp.blogspot.com/-ir0u3LbsJpI/WuLrqmgIUTI/AAAAAAAAMBg/2gIT6YtlP9Q81DzIThG5wW0NLsj00pk6gCK4BGAYYCw/s640/BPMN-Sample_AND-Split-706456.png" width="640" /></a><br />
<br />
Related Article<br />
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259891-M203">M203 (BUSINESS FLOW) Parallel, Single Split and Multiple Split</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259951-M204">M204 (BUSINESS FLOW) Looping Structure</a> (Manual)</li>
</ul>
<br />
<br />
2) <a href="https://en.workflow-sample.net/2011/04/bpmn-splits-for-flexible-flow.html" target="_blank">BPMN Splits for flexible flow conditions</a><br />
<br />
<br />
Among three types of splitting, "OR split (inclusive split)" which flows to "some" that satisfy a condition is explained.<br />
<br />
<div style="text-align: center;">
[BPMN sample-OR split]</div>
<a href="http://1.bp.blogspot.com/-JOaxckqwycw/WuLrq2NNPdI/AAAAAAAAMBs/kqFMbK5M5PsshqaZXV3LHmYIb2aOIc-IACK4BGAYYCw/s1600/BPMN-Sample_OR-Split-707717.png"><img alt="" border="0" height="342" id="BLOGGER_PHOTO_ID_6549055929488063954" src="https://1.bp.blogspot.com/-JOaxckqwycw/WuLrq2NNPdI/AAAAAAAAMBs/kqFMbK5M5PsshqaZXV3LHmYIb2aOIc-IACK4BGAYYCw/s640/BPMN-Sample_OR-Split-707717.png" width="640" /></a><br />
<br />
Related Article<br />
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259891-M203">M203 (BUSINESS FLOW) Parallel, Single Split and Multiple Split</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259951-M204">M204 (BUSINESS FLOW) Looping Structure</a> (Manual)</li>
</ul>
<br />
<br />
3) <a href="https://en.workflow-sample.net/2011/04/automatically-sending-template-emails.html" target="_blank">Automatically Sending Template Emails in the Middle of a Workflow</a><br />
<br />
<br />
A lesson about on of the "Events" in BPMN. There are 14 types of Events that are available in"Questetra BPM Suite", as of May 2018.<br />
<br />
<div style="text-align: center;">
[BPMN sample-Message Throwing Never-Ending]</div>
<div style="text-align: center;">
<a href="http://1.bp.blogspot.com/-y95-q8Cl5BU/WuLrpwadPyI/AAAAAAAAMBE/3Lihq_jMXTwmFmtFTxUYA-3fL33uVolIACK4BGAYYCw/s1600/BPMN-Sample_Message-Throwing-Never-Ending-703404.png"><img alt="" border="0" height="84" id="BLOGGER_PHOTO_ID_6549055910753156898" src="https://1.bp.blogspot.com/-y95-q8Cl5BU/WuLrpwadPyI/AAAAAAAAMBE/3Lihq_jMXTwmFmtFTxUYA-3fL33uVolIACK4BGAYYCw/s640/BPMN-Sample_Message-Throwing-Never-Ending-703404.png" width="640" /></a></div>
<br />
Related Article<br />
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245532-M224">M224 (AUTO EVENT) Auto Sending of Email with Business data Inserted</a> (Manual)</li>
</ul>
<br />
<br />
4) <a href="https://en.workflow-sample.net/2011/04/how-to-design-primary-workflows-with.html" target="_blank">How to Design Primary Workflows With Many Baby Workflows</a><br />
<br />
<br />
A lesson for how to connect Processes using "Throwing Message Intermediate Event (HTTP)".<br />
<br />
<div style="text-align: center;">
[BPMN sample-Generate Twins]</div>
<a href="http://2.bp.blogspot.com/-OLHoBX_6SvY/WuLrpXuAUJI/AAAAAAAAMA8/dWAou341rSks3WvZD1ZwJrtMYOYXo4l8wCK4BGAYYCw/s1600/BPMN_Birth-Twins-701640.png"><img alt="" border="0" height="326" id="BLOGGER_PHOTO_ID_6549055904124260498" src="https://2.bp.blogspot.com/-OLHoBX_6SvY/WuLrpXuAUJI/AAAAAAAAMA8/dWAou341rSks3WvZD1ZwJrtMYOYXo4l8wCK4BGAYYCw/s640/BPMN_Birth-Twins-701640.png" width="640" /></a><br />
<br />
Related Article<br />
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002262731-M411">M411 (PROCESS CONNECTION) Auto-starting "Billing Process" Triggered by "Shipping Process"</a> (Manual)</li>
</ul>
<br />
<br />
<hr />
<br />
<h2>
Basics of BPMN, how to model in Questetra</h2>
<ul>
<li><a href="https://www.questetra.com/ja/features/modeling/bpmn-introduction/" target="_blank">BPMN Introduction</a></li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245032-M201">M201 (DEFINITION GENERAL) Defining Business Process, Running on Workflow</a> (Manual)</li>
</ul>
<br />
(<a href="https://ja.workflow-sample.net/2018/05/bpmn-introduction.html" target="_blank">Japanese Entry (和文記事)</a>)<br />
<br />Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-38649893020541856442018-04-22T16:00:00.000-04:002018-04-22T16:00:15.107-04:00Episode 584: "Leave Application", be Sure and in Advance!<div class="mobile-photo">
<div class="separator" style="clear: both; text-align: center;">
<img border="0" data-original-height="630" data-original-width="1200" height="336" src="https://3.bp.blogspot.com/-f2EfXjXKqiQ/WtmJNEz9TLI/AAAAAAAAAO4/WOUqPHshRrAq0Zx7LJCuD827JAAO0gTMACLcBGAs/s640/20180423-Leave_Request.png" width="640" /></div>
<br />In the "<a href="https://en.workflow-sample.net/2018/04/attendance-report-improve.html" target="_blank">Hours Worked Report flow</a>" which I showed the other day, it has been designed that the working status becomes "Vacation" when the deadline passed without reporting one's attendance. Does it mean that it is possible for the person him/herself or the boss or the management to confirm the days when the vacations were taken just by looking at the processing record of the "Attendance Report flow", which is actually the attendance record?</div>
<br />
No, Wait a minute... There could be a possibility of a case where it has been recorded as vacation despite worked, because forgotten reporting. In the first place, a "vacation" should be given only after you apply in advance and your boss approves it.<br />
<br />
The management department checks the monthly service record by matching "Leave application" and "Attendance record (record of Hours-worked reports)". In case if an employee is recorded as on vacation on the attendance record, but the corresponding application has not been submitted, you need a correction of attendance record (reapplication) or to ask submission of leave application (Post-application). In order to reduce the extra labor in the management department, it is desirable to correctly make attendance reports and leave applications, and to confirm oneself whether there are omissions at the end of the month.<br />
<br />
<br />
<div style="text-align: center;">
[Leave Request Flow]</div>
<a href="http://1.bp.blogspot.com/-AzaS7aqK-_8/WthHDUs9a5I/AAAAAAAAMAE/LzNEq_8Atjoa5Gt55fRJHn4EFlt86XJ1gCK4BGAYYCw/s1600/20180422-en-705797.png"><img alt="" border="0" height="280" id="BLOGGER_PHOTO_ID_6546060180805479314" src="https://1.bp.blogspot.com/-AzaS7aqK-_8/WthHDUs9a5I/AAAAAAAAMAE/LzNEq_8Atjoa5Gt55fRJHn4EFlt86XJ1gCK4BGAYYCw/s640/20180422-en-705797.png" width="640" /></a><br />
<br />
<a name='more'></a><br />
"Leave application" should be made in advance to the day of getting a vacation and should be approved by the superior. So that one can coordinate work such as asking colleagues to respond when away from the office. Sometimes, however, you may wake up in one morning and find you cannot come to the office because of a cold or sickness. In that respect, if it is a cloud-based Workflow, you can make your application for leave of absence in your bed with your smartphone.<br />
<br />
In addition, in this "Leave Request flow", you can refer to the company's work manual. Since it is "Leave application", I suppose you can understand the contents to be filled in roughly when you look at the screen of the input form, but it is convenient to be able to browse manuals and regulations related to work while making your application. If the work manual is properly maintained, there are advantages such as reducing answers to frequently asked questions or avoiding unnecessary reworking in later Steps. This can also be said to be one of "business improvements".<br />
<br />
<div style="text-align: center;">
<Example of Work manual></div>
<div style="text-align: center;">
<a href="http://1.bp.blogspot.com/-9T8UmKH9qa4/WthHDH9i9YI/AAAAAAAAL_0/LsqmRswUK_YWGDh-HzmxqsRbrEZlqMy-ACK4BGAYYCw/s1600/20180422-m-en-704612.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6546060177385387394" src="https://1.bp.blogspot.com/-9T8UmKH9qa4/WthHDH9i9YI/AAAAAAAAL_0/LsqmRswUK_YWGDh-HzmxqsRbrEZlqMy-ACK4BGAYYCw/s640/20180422-m-en-704612.png" width="446" /></a></div>
<br />
<div style="text-align: center;">
<Operating screen></div>
<div style="text-align: center;">
<a href="http://2.bp.blogspot.com/-zhvziECF1Cw/WthHCkQpIcI/AAAAAAAAL_o/xWrEF9FEAY4igGl-SMS2sQ1y3JQqYdNRwCK4BGAYYCw/s1600/20180422-f-en-702736.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6546060167801807298" src="https://2.bp.blogspot.com/-zhvziECF1Cw/WthHCkQpIcI/AAAAAAAAL_o/xWrEF9FEAY4igGl-SMS2sQ1y3JQqYdNRwCK4BGAYYCw/s640/20180422-f-en-702736.png" width="336" /></a></div>
<br />
<div style="text-align: center;">
<Data Items list></div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-XKeDuzbTnnM/WthHCUj7nPI/AAAAAAAAL_c/C9ZJDTtzDqUpR99CiF6oR-jGw1ckQAwqgCK4BGAYYCw/s1600/20180422-d-en-701179.png"><img alt="" border="0" height="394" id="BLOGGER_PHOTO_ID_6546060163587742962" src="https://3.bp.blogspot.com/-XKeDuzbTnnM/WthHCUj7nPI/AAAAAAAAL_c/C9ZJDTtzDqUpR99CiF6oR-jGw1ckQAwqgCK4BGAYYCw/s640/20180422-d-en-701179.png" width="640" /></a></div>
<div style="text-align: center;">
<br /></div>
[Free download]<br />
Business Template: <a href="https://questetra.github.io/app-templates/en/20180423-Leave_Request-en.qar" target="_blank">Daily Report</a><br />
<br />
<hr />
<h2>
Similar Models</h2>
<br />
<ul>
<li><a href="https://en.workflow-sample.net/2013/10/manual.html">Business Manual within Workflow!</a> (2013-10-07)</li>
<li><a href="https://en.workflow-sample.net/2013/03/leave-request.html">With Cloud, Leave Request at Any Time from Smartphone!</a> (2013-03-04)</li>
<li><a href="https://en.workflow-sample.net/2011/04/blog-post_12.html">An Absence Registering Workflow Connected to "Number-of-Remaining-Paid-Holidays" Reminders</a> (2011-04-12)</li>
</ul>
<br />
<h2>
Related Articles</h2>
<ul>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002260311-M214">M214 (OPERATING SCREEN) 'Work Manual' referred from Operating Screen</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002245532-M224">M224 (AUTO EVENT) Auto Sending of Email with Business data Inserted</a> (Manual)</li>
<li><a href="https://questetra.zendesk.com/hc/en-us/articles/360002259891-M203">M203 (BUSINESS FLOW) Parallel, Single Split and Multiple Split</a> (Manual)</li>
</ul>
<br />
(<a href="https://en.workflow-sample.net/2018/04/leave-request.html">Japanese Entry (和文記事)</a>)Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-53199466394948960092018-04-15T16:00:00.000-04:002018-05-23T03:40:16.022-04:00Episode 583: Process Improvement by Integrating Similar Workflows<div class="mobile-photo">
<div class="separator" style="clear: both; text-align: center;">
<img border="0" data-original-height="630" data-original-width="1200" height="336" src="https://2.bp.blogspot.com/-SIlOwpUccao/WtKwBlgf0XI/AAAAAAAAAOM/FlL4568AJ7QFqEAIPVqYADis4psGS2I3QCLcBGAs/s640/583.png" width="640" /></div>
In Japan, half a month has passed since a new fiscal year started, so I guess the new hires are getting used to their new environment.</div>
<br />
In the past two weeks, we introduced workflows for "Attendance report flow" and "Daily report flow" oriented (not necessarily) for new employees. If you've "reported" properly every day, I suppose you thoroughly got used to operations of the Workflow platform.<br />
<ul>
<li><a href="https://en.workflow-sample.net/2018/04/attendance-report-improve.html" target="_blank">Episode 581: Rookies, Get Used to Workflow in Attendance Report!</a></li>
<li><a href="https://en.workflow-sample.net/2018/04/daily-report.html" target="_blank">Episode 582: Look Back on the Day with a Daily Business Report</a>!</li>
</ul>
When you compare these two Workflows, you will recognize that they are very similar<br />
<ul>
<li>It is automatically started and appears in [My Tasks] of all employees every morning</li>
<li>An employee reports, the boss (a leader) confirms.</li>
<li>The deadline has been set and if it is not finished until, it automatically terminates</li>
</ul>
<br />
Even though the contents to be reported are different as "work time" and "work contents" depending on the Workflows, their outlines are almost the same. Then, why don't you put these together?<br />
<br />
<div style="text-align: center;">
[Attendance-Work Report]</div>
<div style="text-align: center;">
<a href="http://2.bp.blogspot.com/-HNnQbGyWxps/WtBy5g5lR5I/AAAAAAAAL9M/kxhCQU3PtlEbObxIpXbW3bj6dhqQIwtxACK4BGAYYCw/s1600/20180416-attendance-daily-report-model-en-741200.png"><img alt="" border="0" height="264" id="BLOGGER_PHOTO_ID_6543856590978893714" src="https://2.bp.blogspot.com/-HNnQbGyWxps/WtBy5g5lR5I/AAAAAAAAL9M/kxhCQU3PtlEbObxIpXbW3bj6dhqQIwtxACK4BGAYYCw/s640/20180416-attendance-daily-report-model-en-741200.png" width="640" /></a></div>
<br />
<a name='more'></a><br />
Based on the "Hours Worked Report" in Episode 581, I made some improvements to make it capable of reporting "work content" as well. With this, it is now possible to report/check "work time" and "work content" of that day in one Workflow! It is now convenient, isn't it?<br />
<br />
You can complete a new Workflow in ten minutes or less since the changes are few. It is not a good idea to include too much of this and that in one Workflow definition, but by integrating similar flows, users can complete their reporting with fewer operations. Even though the changes are few, the effect of the improvement will be great if the Workflow is used by many people every day.<br />
(On the other hand, splitting a grand Workflow that is too complicated will lead to big business improvement.)<br />
<br />
As you use and operate Workflows every day, it is very important to keep improving them continuously. It is often happening to become easy for the user to use just by changing a Data Item name or adding an explanation. In addition, it is also important to instantly reflect it in the Workflow definition when the business rule changes. Always try to be flexible for modification/improvement according to your organization and users.<br />
<div style="text-align: center;">
<br /></div>
<div style="text-align: center;">
<Operating screen: "2. Enter leaving time/work content"></div>
<div style="text-align: center;">
<a href="http://1.bp.blogspot.com/-QXMyRGjkYbY/WtBy6UNd_aI/AAAAAAAAL9c/Q7zJJTJmVbMfcBYuHiBdgTkI6_J4cItPwCK4BGAYYCw/s1600/20180416-attendance-daily-report-op-en-744238.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6543856604752510370" src="https://1.bp.blogspot.com/-QXMyRGjkYbY/WtBy6UNd_aI/AAAAAAAAL9c/Q7zJJTJmVbMfcBYuHiBdgTkI6_J4cItPwCK4BGAYYCw/s640/20180416-attendance-daily-report-op-en-744238.png" width="324" /></a></div>
<br />
<div style="text-align: center;">
<Data Items list></div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-oyOqLzYBFiM/WtBy5F6A0pI/AAAAAAAAL88/7PlWTjgrLmUL90c5OYsHa9SGjRzi2xhSwCK4BGAYYCw/s1600/20180416-attendance-daily-report-data-en-739187.png"><img alt="" border="0" height="430" id="BLOGGER_PHOTO_ID_6543856583732941458" src="https://3.bp.blogspot.com/-oyOqLzYBFiM/WtBy5F6A0pI/AAAAAAAAL88/7PlWTjgrLmUL90c5OYsHa9SGjRzi2xhSwCK4BGAYYCw/s640/20180416-attendance-daily-report-data-en-739187.png" width="640" /></a></div>
<br />
<br />
[Free download]<br />
Business Template: <a href="https://questetra.github.io/app-templates/en/20180416-Attendance-Work_Report-en.qar" target="_blank">Daily Report</a><br />
<br />
<hr />
<br />
<Similar Models><br />
<br />
<ul>
<li><strong>Business Improvement in Hotel Operation</strong></li>
<ul>
<li><a href="https://en.workflow-sample.net/2018/01/process-improvement-hotel1.html">Episode 568 (Part 1)</a> (2018-01-01)</li>
<li><a href="https://en.workflow-sample.net/2018/01/process-improvement-hotel2.html">Episode 569 (Part 2)</a> (2018-01-08)</li>
<li><a href="https://en.workflow-sample.net/2018/01/process-improvement-hotel3.html">Episode 570 (Part 3)</a> (2018-01-14)</li>
</ul>
<li><strong>Business Improvement in Website Operation</strong></li>
<ul>
<li><a href="https://en.workflow-sample.net/2018/01/process-improvement-webmedia1.html">Episode 571: (Part 1) </a> (2018-01-21)</li>
<li><a href="https://en.workflow-sample.net/2018/01/process-improvement-webmedia2.html">Episode 572: (Part 2) </a> (2018-01-28)</li>
<li><a href="https://en.workflow-sample.net/2018/02/process-improvement-webmedia3.html">Episode 573: (Part 3) </a> (2018-02-05)</li>
</ul>
<li><strong>Business Improvement in SaaS Vendor Operation</strong></li>
<ul>
<li><a href="https://en.workflow-sample.net/2018/02/process-improvement-saas-vendor-1.html">Episode 574: (Part 1)</a> (2018-02-13)</li>
<li><a href="https://en.workflow-sample.net/2018/02/process-improvement-saas-vendor-2.html">Episode 575: (Part 2)</a> (2018-02-19)</li>
<li><a href="https://en.workflow-sample.net/2018/02/process-improvement-saas-vendor-3.html">Episode 576: (Part 3)</a> (2018-02-26)</li>
</ul>
</ul>
<br />
<<Related Articles>><br />
<br />
<ul>
<li><a href="http://www.questetra.com/tour/m2/m201/">M201 DEFINITION GENERAL: Defining Business Process, Running on Workflow</a> </li>
<li><a href="http://www.questetra.com/tour/m2/m202/">M202 BUSINESS FLOW: Deadline in Each Step</a></li>
<li><a href="http://www.questetra.com/tour/m2/m230/">M230 AUTOMATED STEP: Auto Executing Complicated Data Processing (ECMAScript)</a></li>
</ul>
<br />
<br />
[<a href="https://ja.workflow-sample.net/2018/04/attendance-daily-report.html" target="_blank">Japanese Entry (和文記事)</a>]Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-55582051542088242382018-04-08T16:00:00.000-04:002018-04-08T16:00:32.873-04:00Episode 582: Look Back on the Day with a Daily Business Report!<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6541242378258039810" src="https://4.bp.blogspot.com/-nM-mz8Q6huA/WscpSTnNRAI/AAAAAAAAL7U/HmwZxvFGPJYajddJRh7XmJjzUsCEs8OIwCK4BGAYYCw/s640/21180409-Daily_Report-771308.png" width="640" /></div>
<div class="mobile-photo">
<br /></div>
In the <a href="http://en.workflow-sample.net/2018/04/attendance-report-improve.htm" target="_blank">previous post</a>, I introduced you the "Hours-worked report" which even new hires make every day. It has been designed considering input effort to be reduced by devising of initial value and input screen so that reports are made properly every day. Speaking everyday report, the daily report is one of them. Whether it is during the training period or after being assigned, it is an important task for new recruits to report the "works done" and "matters learned" to the superiors or to seniors.<br />
<br />
Through the daily report, new hires can learn business etiquette and how to work, and also help them communicate with their boss, seniors or other employees. Above all, the opportunity to look back on the day and organize what you learned or noticed is particularly important to be in the new environment.<br />
<br />
<div style="text-align: center;">
[Daily Report]</div>
<div style="text-align: center;">
<a href="http://4.bp.blogspot.com/-OLKfPEqMduQ/WscpTBsSf-I/AAAAAAAAL7k/KiPoHlKv2mIIlJLYHYRHaPiXNQfddIucgCK4BGAYYCw/s1600/21180409-Daily_Report-model-en-774910.PNG"><img alt="" border="0" height="314" id="BLOGGER_PHOTO_ID_6541242390627385314" src="https://4.bp.blogspot.com/-OLKfPEqMduQ/WscpTBsSf-I/AAAAAAAAL7k/KiPoHlKv2mIIlJLYHYRHaPiXNQfddIucgCK4BGAYYCw/s640/21180409-Daily_Report-model-en-774910.PNG" width="640" /></a></div>
<br />
<a name='more'></a><br />
It is a very simple report flow that automatically starts at 8:30 every morning. Not only new hires but also all employees, a "daily report" task comes on the list of "My Tasks".<br />
<br />
It would be alright to input collectively just before leaving, but my recommendation is to input what you did each time as a memo and save it temporally. New recruits will be able to obtain appropriate feedback from their boss and seniors if they describe unclear points, questions, and consultation matters. (Of course, it is better to ask directly when they do not know ...)<br />
<br />
It is desirable that you leave the company after completing the report every day, but sometimes you may not be able to or may forget it. In this "daily report flow", a deadline is set so that to be automatically terminated as "unreported" when the time comes. It is different from its original purpose if reporting by recalling events of more than a week ago. In order to avoid becoming "unreported", try to handle it properly while it is in [My Tasks].<br />
<br />
<div style="text-align: center;">
<Timer setting screen></div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-eU9UuahYk7U/WscpTrNPEcI/AAAAAAAAL70/tSJcscENg1QAGFZ1NFrh21HgR0k8X_q8wCK4BGAYYCw/s1600/21180409-Daily_Report-setting-en-777691.PNG"><img alt="" border="0" height="524" id="BLOGGER_PHOTO_ID_6541242401771426242" src="https://3.bp.blogspot.com/-eU9UuahYk7U/WscpTrNPEcI/AAAAAAAAL70/tSJcscENg1QAGFZ1NFrh21HgR0k8X_q8wCK4BGAYYCw/s640/21180409-Daily_Report-setting-en-777691.PNG" width="640" /></a></div>
<br />
<div style="text-align: center;">
<Data Items list></div>
<div style="text-align: center;">
<a href="http://2.bp.blogspot.com/-r2yFygA8PVU/WscpUTMbYJI/AAAAAAAAL8E/UxL8eAYTljgBAlnVsNxOGmiNL9K0dj3dQCK4BGAYYCw/s1600/21180409-Daily_Report-data-en-779875.PNG"><img alt="" border="0" height="260" id="BLOGGER_PHOTO_ID_6541242412505456786" src="https://2.bp.blogspot.com/-r2yFygA8PVU/WscpUTMbYJI/AAAAAAAAL8E/UxL8eAYTljgBAlnVsNxOGmiNL9K0dj3dQCK4BGAYYCw/s640/21180409-Daily_Report-data-en-779875.PNG" width="640" /></a></div>
<br />
[Free download]<br />
Business Template: <a href="https://questetra.github.io/app-templates/en/20180409-Daily_Report-en.qar" target="_blank">Daily Report</a><br />
<hr />
<Similar Models><br />
<ul>
<li><strong>Daily report</strong></li>
<ul>
<li><a href="https://en.workflow-sample.net/2013/12/free-trial-report.html">Free Trial of a Workflow, What Do You Run on It? (Daily Report)</a> (2013-12-30)</li>
<li><a href="https://en.workflow-sample.net/2011/11/workflow-definition-that-guides-daily.html">A Workflow Definition that Guides Daily and Weekly Report</a> (2011-11-07)</li>
<li><a href="https://en.workflow-sample.net/2014/09/timer-start.html">'Timer Start' Workflow Adjusts Your Rhythm of Work</a> (2014-09-08)</li>
<li><a href="https://en.workflow-sample.net/2013/09/status-monitoring.html">Accelerate Daily Report Flow with 'HEAT Map'</a> (2013-09-02)</li>
<li><a href="https://en.workflow-sample.net/2014/11/end-timer.html">Create a Mechanism that 'Daily Report' which might have been Piled up, won't be so!</a> (2014-11-04)</li>
<li><a href="https://en.workflow-sample.net/2014/09/telework.html">Remote Work, 'Hours Worked Management' is Important than You Think</a> (2014-09-22)</li>
<li><a href="https://en.workflow-sample.net/2014/12/backend-saas-workflow.html">Using SaaS Workflow for Backend of Smartphone App for Business</a> (2014-12-22)</li>
</ul>
<li><strong>Daily sales report</strong></li>
<ul>
<li><a href="https://en.workflow-sample.net/2013/10/script-api.html">Meanings of Taking In the Meteorological Data to "Daily Reports" (Utilizing Weather API)</a> (2013-10-21)</li>
<li><a href="https://en.workflow-sample.net/2013/10/script-api-2.html">Automatic Conversion of Sales on the Exchange Rate of the Day (Utilizing of Currency API)</a> (2013-10-28)</li>
<li><a href="https://en.workflow-sample.net/2015/10/sales-report.html">Daily Sales Report Referring to Customer Master Data</a> (2015-10-05)</li>
<li><a href="https://en.workflow-sample.net/2015/10/sales-report-geolocation.html">GPS Recording in Daily Report Process</a> (2015-10-19)</li>
</ul>
</ul>
<br />
<<Related Articles>><br />
<ul>
<li><a href="http://www.questetra.com/tour/m2/m217/">M217 AUTO START: Auto Starting at the Time You Fix</a></li>
<li><a href="http://www.questetra.com/tour/m2/m202/">M202 BUSINESS FLOW: Deadline in Each Step</a></li>
<li><a href="http://www.questetra.com/tour/m1/m104/">M104 TASK HANDLING: Jobs in My Tasks</a></li>
</ul>
<br />
<br />
[<a href="https://ja.workflow-sample.net/2018/04/daily-report.html" target="_blank">Japanese Entry (和文記事)</a>]Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-71699748892859322452018-04-01T16:00:00.000-04:002018-04-01T16:00:06.217-04:00Episode 581: Rookies, Get Used to Workflow in Attendance Report!<div class="mobile-photo">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://2.bp.blogspot.com/-HZotx0GSfWk/Wr3PT2ONy3I/AAAAAAAAANg/V7KgD16fGY45ksnwvEM2bhHxdw0Olt_8ACLcBGAs/s1600/20180402EyeCatch.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="630" data-original-width="1200" height="336" src="https://2.bp.blogspot.com/-HZotx0GSfWk/Wr3PT2ONy3I/AAAAAAAAANg/V7KgD16fGY45ksnwvEM2bhHxdw0Olt_8ACLcBGAs/s640/20180402EyeCatch.png" width="640" /></a></div>
In Japan, spring is the season of cherry blossom and the starting of a new life.</div>
<br />
Another new fiscal year begins today, so an employment ceremony is held in many companies. Once a new employee is assigned, the superiors, senior employees, or HR staffs will instruct this and that of company life. Among them, it supposedly includes "how to make work report".<br />
<br />
Recently, "Workstyle reformation" and "Discretionary working time system (Exempt employee)" are topics frequently discussed, so it is very important to be able to record and to recognize the hours worked properly. (Attendance management)<br />
Reporting and recording of attendance and leave time has been managed in various ways, such as by filling in paper or stamping on time cards when it used to be, or now with IC cards or in a dedicated system, etc. Also, to use a general-purpose Workflow system is one of the ways.<br />
<br />
Sometimes "Attendance report flow" is referred to as "the four major Workflow Apps", together with "Work request flow", "Procurement request flow" and "Out-of-pocket expenses claim flow" which I introduced you before as "the Starter templates pack". By managing attendance using cloud-based Workflow, you can take advantages of the following.<br />
<ul>
<li>Teleworkers/Remote workers or staffs with frequent outings can also be recorded in the workplace or on the go</li>
<li>Daily processing allows new members to become accustomed to Workflow operations</li>
<li>Possible to improve ease-of-use for the organization continuously (would lead to reform of work style)</li>
</ul>
<br />
<div style="text-align: center;">
[Hours Worked Report]</div>
<div style="text-align: center;">
<a href="http://1.bp.blogspot.com/-oukYBTmQpuo/Wr2k2UQsJGI/AAAAAAAAL6w/lTxVD_r9r4oWKFEmU5XFgWwRM-XFolZkQCK4BGAYYCw/s1600/20180402-Attendance_Report-m-en-743428.png"><img alt="" border="0" height="320" id="BLOGGER_PHOTO_ID_6538563487070430306" src="https://1.bp.blogspot.com/-oukYBTmQpuo/Wr2k2UQsJGI/AAAAAAAAL6w/lTxVD_r9r4oWKFEmU5XFgWwRM-XFolZkQCK4BGAYYCw/s640/20180402-Attendance_Report-m-en-743428.png" width="640" /></a></div>
<br />
<a name='more'></a><br />
For new recruits, there are lots of new things to remember such as organizations, jobs, systems... If it is necessary to log in to different systems for each purpose, such as Attendance report, Expense adjustment, Leave request, etc. it will be very cumbersome (isn't it?) In that respect, you will be able to minimize what you will learn and to speed up getting accustomed to it if you can realize it all in one Workflow system (Workflow platform).<br />
<br />
In this "Attendance report flow", various measures are taken to prevent omission of reports or to alleviate the operation of inputting.<br />
<br />
<h4>
Auto-start</h4>
In order to minimize the occurrence of "forgetting to report attendance", "My task" of "report attendance time" is automatically allocated every morning. For a worker, he or she only needs to enter the attendance time in response to a request that arrives every morning, so omissions will barely occur. (Incidentally, if he or she leaves the task for 20 hours without entering anything, it will automatically be considered as "vacation day", so he or she does not have to do anything especially during a long vacation, etc.)<br />
<br />
<h4>
Initial value setting</h4>
The fact that the default value (initial value) has been entered in advance is also good in the aspect of lowering "effort of inputting". In other words, you can report without entering numbers on the day you worked as expected such as "9: 00 for work attendance / 17: 00 for leaving / 1 hour for a break".<br />
<br />
<h4>
Input support</h4>
Also, note that the input support buttons are implemented as decoration. Recently "Calendar input" or "Time select input of every 30 minutes" are being used frequently as input support, while in this example, "Frequent candidate buttons" are also listed. It is true that the value to be entered as "time of leaving" is limited among 24 hours of a day, so it can be said that the effort of inputting time worked are greatly reduced.<br />
<br />
<div style="text-align: center;">
[Hours Worked Report:"1. Enter attendance time" screen]</div>
<div style="text-align: center;">
<a href="http://4.bp.blogspot.com/-9NPGhpQMzLo/Wr2k1n7KIMI/AAAAAAAAL6c/_S14KpvrnwYYYjpi1PQbee1OKQZOMLd0gCK4BGAYYCw/s1600/20180402-Attendance_Report-op-en-740986.png"><img alt="" border="0" height="542" id="BLOGGER_PHOTO_ID_6538563475168960706" src="https://4.bp.blogspot.com/-9NPGhpQMzLo/Wr2k1n7KIMI/AAAAAAAAL6c/_S14KpvrnwYYYjpi1PQbee1OKQZOMLd0gCK4BGAYYCw/s640/20180402-Attendance_Report-op-en-740986.png" width="640" /></a></div>
<br />
<br />
<div style="text-align: center;">
<Data Items list></div>
<div style="text-align: center;">
<a href="http://2.bp.blogspot.com/-iBcD3UZXk18/Wr2k1O9G_GI/AAAAAAAAL6I/iZ2Kxqxr_XwUiygd4z9faqEJqi8V-hftACK4BGAYYCw/s1600/20180402-Attendance_Report-data-en-739083.png"><img alt="" border="0" height="360" id="BLOGGER_PHOTO_ID_6538563468466256994" src="https://2.bp.blogspot.com/-iBcD3UZXk18/Wr2k1O9G_GI/AAAAAAAAL6I/iZ2Kxqxr_XwUiygd4z9faqEJqi8V-hftACK4BGAYYCw/s640/20180402-Attendance_Report-data-en-739083.png" width="640" /></a></div>
<br />
[Free download]<br />
<ul>
<li>Business Template: <a href="https://questetra.github.io/app-templates/en/20180402-Attendance_Report-en.qar" target="_blank">Hours Worked Report</a></li>
</ul>
<br />
<Similar Models><br />
<ul>
<li><a href="http://en.workflow-sample.net/2014/01/timecard.html">Attendance Time and Leaving Time in Workflow!</a> (2014-01-20)</li>
<li><a href="http://en.workflow-sample.net/2016/01/attendance-report.html">Episode 465: Attendance Management in Cloud-based Workflow!</a> (2016-01-12)</li>
<li><a href="http://en.workflow-sample.net/2016/02/attendance-report.html">Episode 472: Detect Signs of Flu in Business System?</a> (2016-02-29)</li>
<li><a href="http://en.workflow-sample.net/2017/02/attendance-report.html">Episode 523: Tracking the Hours Worked on Cloud</a> (2017-02-20)</li>
<li><a href="http://en.workflow-sample.net/2017/02/process-automation.html">Episode 524: Automation of Work with Server-side JavaScript</a> (2017-02-27)</li>
<li><a href="http://en.workflow-sample.net/2017/05/attendance-report-improve.html">Episode 535: True Work Style Reformation is to Improve the System Continuously</a> (2017-05-15)</li>
</ul>
<br />
<br />
<<Related Articles>><br />
<br />
<ul>
<li><a href="https://www.questetra.com/tour/m2/m218/">M218 AUTO START: Auto Starting Triggered by Incoming Email</a></li>
<li><a href="https://www.questetra.com/tour/m2/m230/">M230 AUTOMATED STEP: Auto Executing Complicated Data Processing (ECMAScript)</a></li>
<li><a href="https://www.questetra.com/tour/m2/m227/">M227 AUTOMATED STEP: Auto Executing Data Binding, Arithmetic Operations</a></li>
<li> <a href="https://www.questetra.com//tour/m4/m405/">M405 DATA ITEMS: Setting: Strings that have been Processed or Converted to be Set in Midstream</a></li>
</ul>
<br />
<br />
[<a href="http://ja.workflow-sample.net/2018/04/attendance-report.html" target="_blank">Japanese Entry (和文記事)</a>]Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-23769772286292927562018-03-25T16:00:00.000-04:002018-03-26T20:52:45.774-04:00Episode 580: Starter Template (3) Out-of-pocket Expenses Claim<div class="mobile-photo">
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6536023016338454018" src="https://1.bp.blogspot.com/-NVeeMIkbgRg/WrSeTdShdgI/AAAAAAAAL5Y/PXJhchjclQgCTdZmFM_qew5Y_PCW96UbwCK4BGAYYCw/s640/20160104-Expense_Claim-744034.png" width="640" /></div>
Continuing the past two weeks, I will introduce you the operation of "Starter Template" which has been pre-installed in the cloud-based Workflow, "Questetra BPM Suite".<br />
<br />
The third one is "Out-of-pocket Expenses reimbursement claim".<br />
<a href="http://en.workflow-sample.net/2016/01/starter-templates-2016-expense-claim.html" target="_blank">Episode 464: Out-of-pocket Expenses Reimbursement Claim (Starter Template)</a> (2016-01-04)<br />
<br />
It is a business flow to make an application for claiming with email attachment of images of receipts taken with a mobile camera. And there is a focus on making it easier to manage receipt images by applying sequentially. Therefore, this will be a business process which is on the premise that "regulation that allows discarding the original paper receipt by taking a receipt image with a mobile camera".<br />
<br />
<div style="text-align: center;">
[Out-of-pocket Expenses claim]</div>
<div style="text-align: center;">
<a href="http://1.bp.blogspot.com/-KFPRumfXr2s/WrSeQpnkWBI/AAAAAAAAL44/C2Xhj7-rm9UxQTh-a4-JFPu5PBdNYfkHgCK4BGAYYCw/s1600/20180326-expense-claim-model-en-732967.png"><img alt="" border="0" height="324" id="BLOGGER_PHOTO_ID_6536022968108341266" src="https://1.bp.blogspot.com/-KFPRumfXr2s/WrSeQpnkWBI/AAAAAAAAL44/C2Xhj7-rm9UxQTh-a4-JFPu5PBdNYfkHgCK4BGAYYCw/s640/20180326-expense-claim-model-en-732967.png" width="640" /></a></div>
<br />
<br />
<a name='more'></a>Even though in this Workflow, applications will be made sequentially each time out-of-pocket expense occurs, there may be considered operations that applications are made once in a month collectively. Perhaps for organizations in which applications were being made in paper may fit with the monthly collective application. There may be considered for the monthly collective application that to Start applications for each every employee collectively, or to automatically generate PDF application form. Below is a list of various examples introduced in articles so far, please refer to it.<br />
<br />
By the way, in order to use "Email Start", it is necessary to set the setting to "enable" on the Workflow platform (the initial state is "disabled"). So, please log in as a user with System administrator authority and make the setting to enable at [Message Start Event (Email)] in [App External Connectivity] in [System Setting].<br />
(See the details here.=> <a href="http://www.questetra.com/tour/m3/m318/">http://www.questetra.com/tour/m3/m318/</a>)<br />
<br />
<div style="text-align: center;">
[Out-of-pocket Expenses claim]</div>
<div style="text-align: center;">
<a href="http://1.bp.blogspot.com/-GraaL1OqXWs/WrSeRajtw_I/AAAAAAAAL5A/AnO39n4WUJgiURmwO9rs16PvJ7TgZcRDwCK4BGAYYCw/s1600/20180326-expense-claim-op-en-736193.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6536022981245518834" src="https://1.bp.blogspot.com/-GraaL1OqXWs/WrSeRajtw_I/AAAAAAAAL5A/AnO39n4WUJgiURmwO9rs16PvJ7TgZcRDwCK4BGAYYCw/s640/20180326-expense-claim-op-en-736193.png" width="302" /></a></div>
<br />
<div style="text-align: center;">
<Data Items list></div>
<div style="text-align: center;">
<a href="http://2.bp.blogspot.com/-rtXglF28Ixw/WrSeSnu5FkI/AAAAAAAAL5Q/pujUp4aGo5kzAgOMIAYLv6-Gd98mzXGjwCK4BGAYYCw/s1600/20180326-expense-claim-data-en-741456.png"><img alt="" border="0" id="BLOGGER_PHOTO_ID_6536023001961928258" src="https://2.bp.blogspot.com/-rtXglF28Ixw/WrSeSnu5FkI/AAAAAAAAL5Q/pujUp4aGo5kzAgOMIAYLv6-Gd98mzXGjwCK4BGAYYCw/s320/20180326-expense-claim-data-en-741456.png" /></a></div>
<br />
[Free download]<br />
<br />
<ul>
<li>Business Template: <a href="https://questetra.github.io/app-templates/en/20180326-Expense_Claim-en.qar" target="_blank">Procurement Request flow</a></li>
</ul>
<br />
<hr />
<br />
<list claim="" concerning="" of="" reimbursement="" workflows="" xpense=""></list><br />
<List of Workflows concerning "Expense reimbursement claim"><br />
<br />
<ul>
<li><strong>Series</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2017/10/expense-claim-1.html">Episode 559: Reason for Not Using Cloud Expense Management System(1) </a> (2017-10-30)</li>
<li><a href="http://en.workflow-sample.net/2017/11/expense-claim-2.html">Episode 560: Reason for Not Using Cloud Expense Management System(2) </a> (2017-11-06)</li>
<li><a href="http://en.workflow-sample.net/2017/11/expense-claim-3.html">Episode 561: Reason for Not Using Cloud Expense Management System </a> (2017-11-13)</li>
<li><a href="http://en.workflow-sample.net/2017/11/expense-claim-4.html">Episode 562: Reason for Not Using Cloud Expense Management System </a> (2017-11-20)</li>
</ul>
<li><strong>Online-ization/Receipts storage</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2015/01/expense-claim.html">Let the Expense Claim Go Online Completely! (Electronic form storage method)</a> (2015-01-26)</li>
<li><a href="http://en.workflow-sample.net/2015/01/scan-to-workflow.html">"Scan & Save" the Receipts</a> (2015-01-19)</li>
<li><a href="http://en.workflow-sample.net/2012/03/blog-post_12.html">Workflow to Cut 80% of the Cost of Administrative Processing on Expense Reimbursement</a> (2012-03-12)</li>
</ul>
<li><strong>Application form PDF Auto-generation</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2013/04/expense-claim-pdf.html">Wow! Expense Reimbursement Claim forms Generated Automatically?</a> (2013-04-30)</li>
<li><a href="http://en.workflow-sample.net/2013/07/expense-claim.html">Expense Claim, Monthly Auto-Start, PDF Auto-Generation</a> (2013-07-01)</li>
</ul>
<li><strong>Data correction/Fraud prevention</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2015/05/expense-claim-2.html">Not Directly Modify Expense Paid Data!</a> (2015-05-11)</li>
<li><a href="http://en.workflow-sample.net/2016/11/expense-claim.html">Episode 510: "Post Facto Approval" in Expense Report Flow is Good Enough</a> (2016-11-21)</li>
<li><a href="http://en.workflow-sample.net/2015/02/expense-claim-2.html">Reimbursement for Out-of-Pocket Expenses in Your Company, Does the Business Flow Prevent 'Fraud'?</a> (2015-02-02)</li>
</ul>
<li><strong>Sequential application</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2010/11/blog-post_08.html">A Workflow to Help Out With the Dreary Month-End Duties</a> (2010-11-08) </li>
</ul>
<li><strong>Monthly application</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2011/05/blog-post_21.html">Clock Register to Launch Application Advances Paid Process automatically Every Month</a> (2011-05-21)</li>
<li><a href="http://en.workflow-sample.net/2013/04/expense-claim.html">Expense Reimbursement Claim; How to make All the Employees to Keep the Deadline 'on Every 5th of the Month'</a> (2013-04-15)</li>
</ul>
<li><strong>Input form</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2010/12/blog-post_28.html">Application Forms for Reimbursement of Expenses Should be Unequivocally Understandable</a> (2010-12-28)</li>
<li><a href="http://en.workflow-sample.net/2011/03/blog-post_02.html">How an Application Form Should Look (Expense Report Sample)</a> (2011-03-02)</li>
<li><a href="http://en.workflow-sample.net/2011/03/blog-post_03.html">Adding General Affair's Hopes in Application Forms</a> (2011-03-03)</li>
</ul>
<li><strong>Notification</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2010/12/blog-post_29.html">The "Let Me Know When My Application for Reimbursement Is Approved" Workflow</a> (2010-12-29)</li>
</ul>
<li><strong>Data utilizing/Analysis</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2015/05/expense-claim-1.html">Output Necessary Items out of Expense Paid Data in Table Type into CSV</a> (2015-05-04) </li>
</ul>
</ul>
<br />
<list claim="" concerning="" of="" reimbursement="" workflows="" xpense=""><related articles=""><br /></related></list> <list claim="" concerning="" of="" reimbursement="" workflows="" xpense=""><related articles=""><<Related Articles>></related></list><br />
<br />
<ul>
<li> <a href="http://www.questetra.com/tour/m2/m218/">M218 AUTO START: Auto Starting Triggered by Incoming Email</a></li>
<li> <a href="https://www.questetra.com/tour/m2/m230/">M230 AUTOMATED STEPLast updated Oct 31, 2017 Auto Executing Complicated Data Processing (ECMAScript)</a></li>
<li> <a href="https://www.questetra.com/tour/m2/m227/">M227 AUTOMATED STEP; Auto Executing Data Binding, Arithmetic Operations</a> </li>
<li><a href="https://www.questetra.com/tour/m4/m405/">M405 DATA ITEMSL: Setting: Strings that have been Processed or Converted to be Set in Midstream</a></li>
</ul>
<div>
<br /></div>
[<a href="http://ja.workflow-sample.net/2018/03/expense-claim.html">Japanese Entry (和文記事)</a>]Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-20039868213905813232018-03-18T16:00:00.000-04:002018-03-18T16:00:18.989-04:00Episode 579: Starter Template (2) Procurement Request flow<div class="separator" style="clear: both; text-align: center;">
<img border="0" data-original-height="630" data-original-width="1200" height="336" src="https://3.bp.blogspot.com/-1NHpb04ejtU/WqttjlLi-9I/AAAAAAAAAM4/EcIK0lsLIYwmy61mdcrkcutnQ_I4qeMFQCLcBGAs/s640/20180319-Purchasing-ja.png" width="640" /></div>
<div class="mobile-photo">
Continuing from the last week, I will introduce you the operation of "Starter Template" which has been pre-installed in the cloud-based Workflow, "Questetra BPM Suite".</div>
<br />
The second one is "Procurement Request".
<br />
<a href="http://en.workflow-sample.net/2015/12/starter-templates-2016-procurement-request.html">Episode 463: Procurement Request (Starter Template)</a> (2015-12-28)
<br />
<br />
It is a business flow that allows anyone to make requests for purchasing from consumables to equipment as long as they are employees. Since status management such as "Decision pending " or "Delivery waiting" is automated, you can check progress at any time.
<br />
<br />
<div style="text-align: center;">
[Procurement Request flow]
</div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-ExmPHppr0Rc/Wqtjg61icII/AAAAAAAAL3E/1RLLfAcv5bgmpCtZIhK3BjWTWMXyFnBdQCK4BGAYYCw/s1600/201803-purchasing-m-en-769461.png"><img alt="" border="0" height="427" id="BLOGGER_PHOTO_ID_6533425101631811714" src="https://3.bp.blogspot.com/-ExmPHppr0Rc/Wqtjg61icII/AAAAAAAAL3E/1RLLfAcv5bgmpCtZIhK3BjWTWMXyFnBdQCK4BGAYYCw/s640/201803-purchasing-m-en-769461.png" width="640" /></a></div>
<br />
<a name='more'></a><br />
In the case of "request for purchasing of the amount exceeding 100,000 JPY", "to have been approved at the 'Decision-making flow' in advance" will be the "purchase condition". On the input screen, it has been given a decoration (display of input hints) which asks for inputting of "related approval process ID" when "total purchase amount" is "100,000 JPY or more".
<br />
<br />
Designing a screen that is easy for users to input is also one of the ways of business improvement. Users will be able to enter necessary items efficiently and smoothly by appropriately describing examples or explanations of contents to be entered on the input screen. On the other hand, "too much decoration" on a screen may degrade easiness of maintenance. It is important to design in consideration its convenience and maintainability, and also to improve along with its operation.
<br />
<br />
<div style="text-align: center;">
[Procurement Request flow:"1. Request Purchasing" screen]
</div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-xRMeJSEqce4/Wqtjh2jCWQI/AAAAAAAAL3Y/p7VbZLNyYf8Zw8Jklw0cZxXrNmsaB0KYACK4BGAYYCw/s1600/201803-purchasing-o-en-773398.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6533425117660338434" src="https://3.bp.blogspot.com/-xRMeJSEqce4/Wqtjh2jCWQI/AAAAAAAAL3Y/p7VbZLNyYf8Zw8Jklw0cZxXrNmsaB0KYACK4BGAYYCw/s640/201803-purchasing-o-en-773398.png" width="392" /></a></div>
<div style="text-align: center;">
<br /></div>
<div style="text-align: center;">
[Data Items list]
</div>
<div style="text-align: center;">
<a href="http://1.bp.blogspot.com/-cPtzmtkt3Vw/WqtjirFlA1I/AAAAAAAAL3o/oWumwvuu9oQ-xapVJJzpUNTwaaKgkRl8wCK4BGAYYCw/s1600/201803-purchasing-d-en-776833.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6533425131763860306" src="https://1.bp.blogspot.com/-cPtzmtkt3Vw/WqtjirFlA1I/AAAAAAAAL3o/oWumwvuu9oQ-xapVJJzpUNTwaaKgkRl8wCK4BGAYYCw/s640/201803-purchasing-d-en-776833.png" width="604" /></a></div>
<br />
[Free download]<br />
<br />
<ul>
<li>Business Template: <a href="https://questetra.github.io/app-templates/en/20180319-Purchasing-en.qar" target="_blank">Procurement Request flow</a></li>
</ul>
<br /><br />
<hr />
<br />
In the past, we also introduced operations related to procurement (purchasing, ordering) of merchandises and management of them as in the following article. Please refer to it together.
<br />
<br />
<List of articles concerning "Procurement / management><br />
<ul>
<li><strong>Purchase / Order</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2013/12/touch-input.html">ISBN by Touch Input</a> (2013-12-09)</li>
<li><a href="http://en.workflow-sample.net/2010/12/blog-post_30.html">Handling Purchase Requests for Office Supplies</a> (2010-12-30)</li>
<li><a href="http://en.workflow-sample.net/2010/12/blog-post_31.html">Adding an Acceptance Testing Workflow to a Purchase Request Workflow</a> (2010-12-31)</li>
<li><a href="http://en.workflow-sample.net/2010/11/blog-post.html">A Strong Order Process Can Become an Intercompany System</a> (2010-11-02)</li>
</ul>
<li><strong>Consumables procurement / Management</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2010/11/blog-post_19.html">Procuring Office Supplies in Large Companies</a> (2010-11-19)</li>
<li><a href="http://en.workflow-sample.net/2012/11/stock-repot.html">Start a Workflow for Stock Supplementation in Dedicated Address</a> (2012-11-19)</li>
<li><a href="http://en.workflow-sample.net/2012/01/blog-post_16.html">Visualizing "Change of Number of Stock" of Revenue Stamps in Graph</a> (2012-01-16)</li>
</ul>
<li><strong>Competitive quotation</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2015/03/competitive-quotes.html">Visualization and Labor Saving on Appraisal of Competitive Quotes</a> (2015-03-23)</li>
<li><a href="http://en.workflow-sample.net/2012/06/blog-post_11.html">Workflow to Obtain Multiple Quotations, and Selection of Contractors</a> (2012-06-11)</li>
</ul>
<li><strong>Lending item management</strong></li>
<ul>
<li><a href="http://en.workflow-sample.net/2017/02/lending-management.html">Episode 522: Want to Manage "Long-term Lending" of Companies Belongings</a> (2017-02-13)</li>
<li><a href="http://en.workflow-sample.net/2012/12/article-management.html">Digitization for Articles Management Tasks of the Administrative Organ</a> (2012-12-17)</li>
</ul>
</ul>
<br />
<<Related Articles>><br />
<ul>
<li><a href="https://www.questetra.com/tour/m2/m201/">M201 DEFINITION GENERAL: Defining Business Process, Running on Workflow</a> </li>
<li><a href="https://www.questetra.com/tour/m2/m207/">M207 DATA ITEM: Initial Value of Data Items Set at the Start</a></li>
<li><a href="https://www.questetra.com/tour/m2/m208/">M208 DATA ITEM: Options at Downstream Step, Set by Upstream Step</a></li>
<li><a href="https://www.questetra.com/tour/m2/m213/">M213 OPERATING SCREEN: Guidance Shown on Operating Screen (HTML/JavaScript)</a></li>
</ul>
<div>
<br /></div>
[<a href="http://ja.workflow-sample.net/2018/03/purchasing.html">Japanese Entry (和文記事)</a>]Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-84743873544929481982018-03-11T16:00:00.000-04:002018-03-11T16:00:22.857-04:00Episode 578: Starter Template (1) Planning-Approval flow<img border="0" src="https://3.bp.blogspot.com/-_BgzdbcvuB0/WqJBd3RCoQI/AAAAAAAAAMU/c7P8v-GI-Cc4Exux0jxGjjGAtu2sE_rqwCLcBGAs/s640/201803-planning-approval.png" width="640" height="336" data-original-width="1200" data-original-height="630" />
<br />
<div class="mobile-photo">In the article of "Episode 577: Work Request Flow is the Basic of Workflow", I introduced you the "Work Request flow" as an operation that I can recommend for any organization. It is one of the business flows (applications) pre-installed in the cloud-based Workflow "Questetra BPM Suite", and there three other business flows are pre-installed. I will introduce you the operation of "Starter Template pack" in three articles in series from this one.</div><br />
The first installment is "Approval flow".<br />
<a href="http://en.workflow-sample.net/2015/12/starter-templates-2016-planning-approval.html">Episode 462: Planning - Approval (Starter Template)</a> (2015-12-21)<br />
<br />
It is a simple business flow in which an employee "applies" a request for approval and the superior of the applicant "approves" it. The flow has been configured that if the external payment amount is 1 million JPY or more, it goes also to the "Approval" by the officer. (Automatically be approved after neglected for 24 hours)<br />
<div style="text-align: center;"><br />
</div><br />
<div style="text-align: center;">[Planning-Approval flow] </div><div style="text-align: center;"><a href="http://2.bp.blogspot.com/-VOegGV6RlJs/WqDvSSryUwI/AAAAAAAAL2k/CltmuGlI-6Ej9K67XrzS_c1uQ5PeQ-2vgCK4BGAYYCw/s1600/20180312-Planning_Approval-en-754192.png"></a><a href="http://2.bp.blogspot.com/-VOegGV6RlJs/WqDvSSryUwI/AAAAAAAAL2k/CltmuGlI-6Ej9K67XrzS_c1uQ5PeQ-2vgCK4BGAYYCw/s1600/20180312-Planning_Approval-en-754192.png"><img alt="" border="0" height="500" id="BLOGGER_PHOTO_ID_6530482557219394306" src="https://2.bp.blogspot.com/-VOegGV6RlJs/WqDvSSryUwI/AAAAAAAAL2k/CltmuGlI-6Ej9K67XrzS_c1uQ5PeQ-2vgCK4BGAYYCw/s1600/20180312-Planning_Approval-en-754192.png" width="640" /></a><br />
<br />
</div><a name='more'></a>"Approval document PDF" are automatically generated for approved plans. It is also possible to print out and use if necessary, for corresponding with audit, etc.<br />
<br />
<div style="text-align: center;"><Example o Auto-generated PDF></div><div style="text-align: center;"><a href="http://1.bp.blogspot.com/-WJ5-BXMSWio/WqDvOaqtlEI/AAAAAAAAL10/G3CCk9pIYnI_f4f9-vkFkniqsXhAOrW0wCK4BGAYYCw/s1600/20180312-Planning_Approval-Png-en-738173.jpg"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6530482490642895938" src="https://1.bp.blogspot.com/-WJ5-BXMSWio/WqDvOaqtlEI/AAAAAAAAL10/G3CCk9pIYnI_f4f9-vkFkniqsXhAOrW0wCK4BGAYYCw/s1600/20180312-Planning_Approval-Png-en-738173.jpg" width="450" /></a></div><br />
<div style="text-align: center;">[Planning-Approval flow:""]</div><div style="text-align: center;"><a href="http://2.bp.blogspot.com/-cEcRzWzYL2E/WqDvPhYB7fI/AAAAAAAAL2E/887C5RmD-Mke6iSnP3zUD62lpfTfFKu-QCK4BGAYYCw/s1600/20180312-Planning_Approval-Op-en-744046.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6530482509623455218" src="https://2.bp.blogspot.com/-cEcRzWzYL2E/WqDvPhYB7fI/AAAAAAAAL2E/887C5RmD-Mke6iSnP3zUD62lpfTfFKu-QCK4BGAYYCw/s1600/20180312-Planning_Approval-Op-en-744046.png" width="314" /></a></div><div style="text-align: center;"><br />
</div><div style="text-align: center;"><Data Items list></div><div style="text-align: center;"><a href="http://1.bp.blogspot.com/-2FqN8dBJN20/WqDvQzEzAnI/AAAAAAAAL2U/BH8O9UoGmZQoNaKmM4uaEvi6M5HQvJr4QCK4BGAYYCw/s1600/20180312-Planning_Approval-Data-en-749181.png"><img alt="" border="0" height="582" id="BLOGGER_PHOTO_ID_6530482531554493042" src="https://1.bp.blogspot.com/-2FqN8dBJN20/WqDvQzEzAnI/AAAAAAAAL2U/BH8O9UoGmZQoNaKmM4uaEvi6M5HQvJr4QCK4BGAYYCw/s1600/20180312-Planning_Approval-Data-en-749181.png" width="640" /></a><br />
<br />
<div style="text-align: left;">[Free download]</div></div><ul style="text-align: start;"><li>Business Template: <a href="https://questetra.github.io/app-templates/en/20180312-Planning_Approval-en.qar" target="_blank">Planning-Approval flow</a></li>
</ul><div><br />
</div><hr /><br />
Regarding 'Flow for requesting approval', I introduced you various alternatives besides this basic form.<br />
<br />
I made a list by theme, please also visit the following articles at the link destination if you are interested.<br />
<ul><li><strong>Approver designation / Approval by other departments / Circulation</strong></li>
<ul><li><a href="http://en.workflow-sample.net/2010/11/blog-post_22.html"> A Ringi Process with Flexibility</a> (2010-11-22)</li>
<li><a href="http://en.workflow-sample.net/2012/05/blog-post_14.html">A Decision Making Flow that Allow to Increase Approver</a> (2012-05-14)</li>
</ul><li><strong>Approval by applicant</strong></li>
<ul><li><a href="http://en.workflow-sample.net/2016/02/approval-request.html">Episode 471: I won't Give an Approval to My Own Application! (by a director of a department)</a> (2016-02-22)</li>
</ul><li><strong>Proxy approval</strong></li>
<ul><li><a href="http://en.workflow-sample.net/2013/02/ringi-proxy.html">Ringi Workflow, How to Design 'Proxy Approval'</a> (2013-02-12)</li>
<li><a href="http://en.workflow-sample.net/2016/03/approval-request.html">Episode 474: Decision-making Flow that Never Allows "Deputy-approval" upon "Over 500 Million JPY"</a> (2016-03-14)</li>
</ul><li><strong>Setting of approver</strong></li>
<ul><li><a href="http://en.workflow-sample.net/2012/01/blog-post_23.html">"Organization" and "Role", Important to Decision Making Workflow</a> (2012-01-23)</li>
<li><a href="http://en.workflow-sample.net/2013/03/ringi-1.html">How to Design a Workflow Chart of Approval Request by the Boss and Their Boss</a> (2013-03-18)</li>
<li><a href="http://en.workflow-sample.net/2013/03/ringi-2.html">How to Design a Workflow Chart of decision making by the Boss and Their Boss: part 2</a> (2013-03-25)</li>
</ul><li><strong>Approval on mobile / Speedy approval</strong></li>
<ul><li><a href="http://en.workflow-sample.net/2011/01/iphone.html">When You Want ANYBODY to Give You That Approval</a> (2011-01-25)</li>
<li><a href="http://en.workflow-sample.net/2011/01/blog-post_27.html">Ringi Process?The Official Approver Gives Comments After the Quick Approval</a> (2011-01-27)</li>
<li><a href="http://en.workflow-sample.net/2011/04/blog-post_29.html">Accelerating Ringi Workflows with Smartphones</a> (2011-04-29)</li>
</ul><li><strong>Time spent on approval</strong></li>
<ul><li><a href="http://en.workflow-sample.net/2014/08/approval-time.html">How Long does it Take to Approve, in Average?</a> (2014-08-25)</li>
<li><a href="http://en.workflow-sample.net/2015/03/quick-approval.html">Pump Up the "Approval Force"(?), A Mysterious Business Processes</a> (2015-03-09)</li>
</ul><li><strong>Approval on budget</strong></li>
<ul><li><a href="http://en.workflow-sample.net/2016/09/planning-approval.html">Episode 501: You Don't Know the Spending of Budget?</a> (2016-09-20) </li>
</ul><li><strong>System migration / Importing past data</strong></li>
<ul><li><a href="http://en.workflow-sample.net/2014/11/bulk-import.html">Importing the Records of Decision-making of the Past in Bulk</a> (2014-11-25)</li>
</ul></ul><ul></ul><span style="background-color: white; color: #444444; font-family: "helvetica" , "arial" , "verdana" , sans-serif; font-size: 16px;"><br />
</span> <span style="background-color: white; color: #444444; font-family: "helvetica" , "arial" , "verdana" , sans-serif; font-size: 16px;"><<Related Articles>></span><br />
<ul><li><a href="http://www.questetra.com/tour/m2/m201/">M201 DEFINITION GENERAL: Defining Business Process, Running on Workflow</a> </li>
<li><a href="https://www.questetra.com/tour/m2/m207/">M207 DATA ITEM: Initial Value of Data Items Set at the Start</a> <a href="https://www.questetra.com/tour/m2/m227/">M227 AUTOMATED STEP: Auto Executing Data Binding, Arithmetic Operations</a> </li>
<li><a href="https://www.questetra.com/tour/m2/m228/">M228 AUTOMATED STEP: Auto Generating PDF File with Business data Inserted</a> </li>
</ul><br />
[<a href="http://ja.workflow-sample.net/2018/03/planning-approval.html">Japanese Entry (和文記事)</a>]Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-87404028141008622042018-03-04T19:51:00.000-05:002019-09-19T04:40:16.217-04:00Episode 577: Work Request Flow is the Basic of Workflow<div class="mobile-photo"><br />
<img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6527888578313278370" src="https://2.bp.blogspot.com/-EfqgH09cMjk/Wpe4E2OxU6I/AAAAAAAAL1I/NzSRkS6FzAoIgG7AT1ASFeuWB2TBeQKMwCK4BGAYYCw/s640/201803-general-work-request-797492.png" width="640" /></div><h2>"What kind of work do you recommend for trying out a Workflow?" </h2>That is a question that frequently asked, and my answer to any kind of organization is always "Work Request flow". "To ask someone to do a (small) job", I suppose it is usually made by email, telephone, verbally, but I tell you that a simple request ought to be made in using Workflow.<br />
<br />
"Workflow" literally means "flow of work", "flow (sequence) of requests for work". In other words, it is the basic (essence) of workflow that "someone requests work from someone" which is the simplest act of doing work in an organization. <br />
<br />
In the cloud-based workflow "Questetra BPM Suite", the following "Work Request flow" is preinstalled and you can try it immediately if you apply for a Free Edition. <br />
<div style="text-align: center;"><br />
</div><div style="text-align: center;">[Work Request flow] </div><div style="text-align: center;"><a href="http://2.bp.blogspot.com/-AXBP-tfpR1Y/Wpe4DU7HJuI/AAAAAAAAL04/ogb7_4cnyGgJHralAdG5hs42F7xB6MsDQCK4BGAYYCw/s1600/20180305-General_Work_Request-en-model-792321.png"><img alt="" border="0" height="198" id="BLOGGER_PHOTO_ID_6527888552192583394" src="https://2.bp.blogspot.com/-AXBP-tfpR1Y/Wpe4DU7HJuI/AAAAAAAAL04/ogb7_4cnyGgJHralAdG5hs42F7xB6MsDQCK4BGAYYCw/s640/20180305-General_Work_Request-en-model-792321.png" width="640" /></a></div><br />
<a name='more'></a><br />
"Work Request flow" is a theme that has been taken up in past articles as well, and a number of examples have introduced so far. Although the viewpoint differs for each article, and each has its own features, you can expect the following effects by submitting work requests using Workflow.<br />
<br />
<dl><dt>Contents of request become clear</dt>
<dd>Prevent ambiguous requests and clarify what to be the deliverable. For a person who received the request, it is also easy to correspond to.</dd>
<dt>Progress becomes obvious</dt>
<dd>You can understand who is holding the job you have requested, and what is going on. For a person who received the request can also decide the priority in corresponding by listing multiple requests.</dd>
<dt>Records are preserved, the achievements can be observed.</dt>
<dd>Even in tasks that are not clearly defined, records of contents of request and correspondence are preserved, which makes it easier to reference later. You can aggregate and analyze, If you have been recorded the cost of corresponding, etc..</dd>
<dt>You can reuse past requests</dt>
<dd>Even contents of rare requests which are made only several times a year, you can also make smoothly by referring to past records.</dd>
<dt>You can visualize "requests" made in-house</dt>
<dd>Jobs which are not defined as a business flow can be clarified. It will be able to see the request relations that who is asking to whom and what, and the request situations.</dd>
<dt>You can design dedicated Business Processes by observing the same type requests.</dt>
<dd>It helps for expanding the range of application of the Workflow by analyzing the results, designing "request" which is, for example, a high occurrence frequency into a new business flow.</dd> </dl>Please refer to articles on the following link, if you have a time for. <br />
I hope you to start using "Work Request flow" which is simple but full of advantages.<br />
<br />
<ul><li><a href="http://en.workflow-sample.net/2011/06/blog-post_27.html">Something Comes Into View Out Of Flow Even From Simple Requests</a> (2011-06-27)</li>
<li><a href="http://en.workflow-sample.net/2011/12/blog-post.html">A Workflow Supposed a Chain of Relegating</a> (2011-12-12)</li>
<li><a href="http://en.workflow-sample.net/2012/06/blog-post_18.html">Inbox is a Graveyard of 'Work Request'</a> (2012-06-08)</li>
<li><a href="http://en.workflow-sample.net/2014/01/free-trial-request.html">Free Trial of a Workflow, What Do You Run on It? (Work Request)</a> (2014-01-06)</li>
<li><a href="http://en.workflow-sample.net/2015/01/happy-new-year-2015.html">"Work Request flow" is good for New Year's Workflow Trial</a> (2015-01-05)</li>
<li><a href="http://en.workflow-sample.net/2015/11/work-request.html">Chain of Request is what Workflow is for (Product Tryout with Simple Requests)</a> (2015-11-09)</li>
<li><a href="http://en.workflow-sample.net/2015/11/work-request-2.html">Work-Request Flow for Recording the Actual Work Cost</a> (2015-11-16) </li>
</ul><br />
<div style="text-align: center;">[Work Request flow:"1. Input Request" screen] </div><articles concerning="" flow="" ork="" request=""></articles><br />
<div style="text-align: center;"><a href="http://3.bp.blogspot.com/-r51gG3BcyDM/Wpe4C1Fm45I/AAAAAAAAL0w/qs9RP6C6Hl4jcI7Jv8srCvCPOb5NNCOSgCK4BGAYYCw/s1600/20180305-General_Work_Request-en-op-789636.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6527888543646671762" src="https://3.bp.blogspot.com/-r51gG3BcyDM/Wpe4C1Fm45I/AAAAAAAAL0w/qs9RP6C6Hl4jcI7Jv8srCvCPOb5NNCOSgCK4BGAYYCw/s640/20180305-General_Work_Request-en-op-789636.png" width="458" /></a></div><br />
<div style="text-align: center;">[Data Items list] </div><div style="text-align: center;"><a href="http://1.bp.blogspot.com/-bV05O6prCWw/Wpe4EJCHibI/AAAAAAAAL1A/b-UW88o-HF0cXr7DZz6IcK5av6KMSC21wCK4BGAYYCw/s1600/20180305-General_Work_Request-en-data-794706.png"><img alt="" border="0" height="366" id="BLOGGER_PHOTO_ID_6527888566180612530" src="https://1.bp.blogspot.com/-bV05O6prCWw/Wpe4EJCHibI/AAAAAAAAL1A/b-UW88o-HF0cXr7DZz6IcK5av6KMSC21wCK4BGAYYCw/s640/20180305-General_Work_Request-en-data-794706.png" width="640" /></a></div><br />
[Free download] <br />
<ul><li>Business Template: <a href="https://questetra.github.io/app-templates/en/20180305-General_Work_Request-en.qar" target="_blank">Work Request Flow</a></li>
</ul><br />
<br />
<<Related Articles>><div><ul><li><a href="https://www.questetra.com/tour/m2/m210/">M210 ALLOCATION: Designation of Downstream Operator in Upstream Step</a></li>
<li> <a href="https://www.questetra.com/tour/m2/m201/">M201 DEFINITION GENERAL: Defining Business Process, Running on Workflow</a></li>
<li><a href="http://www.questetra.com//tour/m1/m115/">M115 AGGREGATION ON ISSUES: Finding Problems of Steps from Data in Closed Issues</a></li>
</ul><articles concerning="" flow="" ork="" request="">[<a href="http://ja.workflow-sample.net/2018/03/general-work-request.html">Japanese Entry (和文記事)</a>]</articles></div>Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-42652888353330135412018-02-26T06:00:00.000-05:002018-03-01T21:25:51.485-05:00Episode 576: Business Improvement in SaaS Vendor Operation (Part 3)<div class="separator" style="clear: both; text-align: center;">
<a href="http://3.bp.blogspot.com/-hUiBxM5YoeU/Wo-w26dyOKI/AAAAAAAALzk/01BS3qp907ANjNMeI4GbND65TerNJrJmwCK4BGAYYCw/s1600/20180226EyeCatch-762797.png" style="margin-left: 1em; margin-right: 1em;"><img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6525628842536745122" src="https://3.bp.blogspot.com/-hUiBxM5YoeU/Wo-w26dyOKI/AAAAAAAALzk/01BS3qp907ANjNMeI4GbND65TerNJrJmwCK4BGAYYCw/s640/20180226EyeCatch-762797.png" width="640" /></a></div>
<h2>
Operation: Creation of Icons, Production of Posters, etc.</h2>
With the new Business Process definition, "requests" from internal company are now managed centrally.<br />
<br />
Those requests of designing from such as the marketing department, the product development department, the sales department, ... are now efficiently handled as a "team". In addition, I suppose that the designers have become interested in each other's work so that contribute to the skill improvement of each designer.<br />
<br />
Reference:<a href="http://en.workflow-sample.net/2018/02/process-improvement-saas-vendor-1.html">Episode 574: Business Improvement in SaaS Vendor Operation (Part 1)</a>、<a href="http://en.workflow-sample.net/2018/02/process-improvement-saas-vendor-2.html">Episode 575: Business Improvement in SaaS Vendor Operation (Part 2)</a><br />
<br />
<h2>
Challenge: Cases where Not In Time for Delivery Schedule</h2>
However, there are still cases where it will not be in time for the "delivery date".<br />
<br />
For example, when a request of "in a haste" comes, "regular requests" are affected. Particularly when large projects such as "release of new service" or "preparation of new campaign" become in action, various "requests in hurry" will occur. As a result, "regular projects that are flexible to deadlines" will not be in time for the due date.<br />
<br />
It should be "a design team that can keep up production schedules" even by utilizing external resources.<br />
<br />
<br />
<div style="text-align: center;">
[Designing request-Outsourcing] </div>
<div style="text-align: center;">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://3.bp.blogspot.com/-zlTbIiAIBsg/WpizolCFhMI/AAAAAAAAALE/0Wp9hLAYOL0Mf01_v_dwI1EArSd6liJcACLcBGAs/s1600/20180226-Designing_request-Outsourcing-en.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="806" data-original-width="855" height="376" src="https://3.bp.blogspot.com/-zlTbIiAIBsg/WpizolCFhMI/AAAAAAAAALE/0Wp9hLAYOL0Mf01_v_dwI1EArSd6liJcACLcBGAs/s400/20180226-Designing_request-Outsourcing-en.png" width="400" /></a></div>
<br /></div>
<br />
<br />
<a name='more'></a><br />
<h2>
Solution: Outsourcing</h2>
Needless to say, "utilization of external resources" in the busy season is effective.<br />
<br />
Certainly, It is also good to nominate the "work staff" inside the company if the personnel system in which "the amount of commission received (contract amount)" is reflected in the evaluation and remuneration of "person in charge of work" is functioning (if directly connected with the increase in revenue of the designer). However, there is a limit even in such "work amount that can be considered positively".<br />
<br />
In this Workflow definition, a flow for Outsourcing has been added.<br />
<br />
Specifically, a route to advance to "3x. Outsource" has been added to the Step of "2. Designate" and "3. Create". (The name of the User type Data Item "Designer" has been changed to "Designer or Outsourcer".) It enables that those which can be entrusted to the outside can be outsourced.<br />
<br />
<br />
<h2>
Discussion: Crowdsourcing</h2>
"Crowdsourcing" (outsourcing to an unspecified number of people) attracts attention along with technology evolution of the Internet and Cloud.<br />
<br />
In Japan as well, the wording that "the worker can engage in the work of other companies, etc. outside the office-hours" is clearly stated in the recommended work rules by the government (February 2018). The number of "people who use own free time for side jobs" are likely to increase even more in the future.<br />
<br />
Of course, there are also "design projects that are not allowed to outsource outside the company" such as "design work based on undisclosed / confidential facts". Therefore, in many companies it is necessary to maintain "design team of certain size" inside.<br />
<br />
However, compared with conventional outsourcing methods (including offshore etc), there are many people who realize that "commission fee" and "time to commissioned management" for crowdsourcing have drastically declined. Regarding "quality" as well, since there is "evaluation system within the crowdsourcing platform", it can be said that it is at a high level in various aspects, such as the delivery time, suggestion quality, the response in communication, and so on. Moreover, there are also other advantages such as "able to reconsider the input and output of the design work" and "You can absorb opinions from an external viewpoint".<br />
<br />
Today, depending on the business process, it can be said that it is worth enough to consider about an idea that "to rely entirely on crowdsourcing" about that particular "Step".<br />
<br />
Incidentally, according to the Japanese Income Tax Law, when paying "writing fee" or "design fee" to an individual, it is necessary to deduct tax according to the payment amount to pay it. ("Withholding obligor" must pay the tax to the government by the 10th of the following month thereafter) And, if there are trustees whose total annual payment exceeds 50,000 JPY, (likewise "Income tax withholding slip" for each employee) there may be cases where you have to prepare "payment report of compensation, fee, contract, or prize" (for national tax authorities, trustee), at the end of a year.<br />
<br />
<Example of accounting process of paying side> Tax rate: 10.21%<br />
Advertisement fee 10.800 / Saving account (Any Bank) 9,779<br />
Withholding (Income tax) 1,021<br />
<br />
However, regarding "Individual number" that is necessary upon that procedure, (although it depends on the communication method during consignment work), that "identity verification" is not easy. Especially about "spoofing", there is a possibility that it can not be detected at all. Utilization of crowdsourcing may be influenced by the aspect of avoiding risks on compliance, and in some cases it may be necessary to devise management measures such as "do not depend heavily on a particular trustee".<br />
<br />
<div style="text-align: center;">
[Designing request-Outsourcing:"3x. Outsource" screen]</div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-8zeoJbuL0Ug/Wo-w2tCz7YI/AAAAAAAALzU/Ojzqw6Bllhs-jYxeDbzzwNuSeBiK4EOIwCK4BGAYYCw/s1600/20180226_Form-en-760503.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6525628838933949826" src="https://3.bp.blogspot.com/-8zeoJbuL0Ug/Wo-w2tCz7YI/AAAAAAAALzU/Ojzqw6Bllhs-jYxeDbzzwNuSeBiK4EOIwCK4BGAYYCw/s640/20180226_Form-en-760503.png" width="288" /></a></div>
<br />
<div style="text-align: center;">
<Data Items list></div>
<div style="text-align: center;">
<a href="http://4.bp.blogspot.com/-C7tXDxzJa7o/Wo-w14hnpEI/AAAAAAAALzE/AEOJA3DDU4EA3Z3NGoPZdPa15vUaZRlSACK4BGAYYCw/s1600/20180226_Data-en-757101.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6525628824836088898" src="https://4.bp.blogspot.com/-C7tXDxzJa7o/Wo-w14hnpEI/AAAAAAAALzE/AEOJA3DDU4EA3Z3NGoPZdPa15vUaZRlSACK4BGAYYCw/s640/20180226_Data-en-757101.png" width="602" /></a></div>
<br />
<br />
[Free download]<br />
<ul>
<li>Business Template: <a href="https://questetra.github.io/app-templates/en/20180226-Designing_request-Outsourcing-en.qar" target="_blank">Designing Request</a></li>
</ul>
< Similar Models ><br />
<ul>
<li><a href="http://en.workflow-sample.net/2017/04/paypal-invoice.html">Episode 529: Making PayPal Operation into Subroutine</a>(2017-04-03)</li>
<li><a href="http://en.workflow-sample.net/2016/12/contract-approval.html">Episode 515: Approval on Contract through Workflow! (Improved version)</a>(2016-12-26)</li>
<li><a href="http://en.workflow-sample.net/2016/03/cartoon-creation.html">Episode 475: Business Process that Finishes "Manga" upon Creating "Scenario"</a> (2016-03-22)</li>
</ul>
<br />
<< Related Articles >><br />
<ul>
<li><a href="https://www.questetra.com/tour/m4/m413/" target="_blank">M413 PROCESS CONNECTION: Setting: Calling Sub-process in the Middle of the Flow, Standing by the Result of It</a></li>
<li><a href="https://www.questetra.com/tour/m2/m226/" target="_blank">M226 AUTO EVENT: Standing by HTTP Request</a></li>
<li><a href="https://www.questetra.com/tour/m2/m210/" target="_blank">M210 ALLOCATION: Designation of Downstream Operator in Upstream Step</a></li>
</ul>
<br />
<br />
[<a href="http://ja.workflow-sample.net/2018/02/process-improvement-saas-vendor-3.html" target="_blank">Japanese Entry (和文記事)</a>]Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-24424155146082535662018-02-19T06:00:00.000-05:002018-02-19T06:00:38.007-05:00Episode 575: Business Improvement in SaaS Vendor Operation (Part 2)<div class="separator" style="clear: both; text-align: center;">
<a href="https://1.bp.blogspot.com/-g-dr8EJf2lo/WoZEKBPktHI/AAAAAAAAAKI/R132zcNEbAk3I86KtFLC1MH_8L4VI44FQCLcBGAs/s1600/20180219EyeCatch.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="630" data-original-width="1200" height="336" src="https://1.bp.blogspot.com/-g-dr8EJf2lo/WoZEKBPktHI/AAAAAAAAAKI/R132zcNEbAk3I86KtFLC1MH_8L4VI44FQCLcBGAs/s640/20180219EyeCatch.png" width="640" /></a></div>
<h2>
Business: Design Production</h2>
A design team where "requests" from in-house come in one after another.<br />
<br />
By improving the "Request form" (Starting step) of design creation, it has become possible to handle requests more stably than before. (Reference: <a href="http://en.workflow-sample.net/2018/02/process-improvement-saas-vendor-1.html">"Episode 574: Business Improvement in SaaS Vendor Operation (Part 1)</a>")<br />
<br />
As we also prepared an automatic start event (Message Start Event), cases where the Process of "Designing request" is used as "sub-process" have increased as well. In other words, cooperation between business processes has been automated with API POST communication, by placing "call event" and "standby event" in the Business Process diagram (main process) of Sales department or Manufacturing department. (In short, the Process is started with data such as "title of requested item" or "details of requested work", and data such as "design report text" and "deliverable file" is returned at the same time when the work is completed.)
<br />
<br />
Furthermore, as we also opened to in-house the sample of the main Process to call out the "sub-process", designing work in various departments are to be integrated into the Process of "Designing request" in the future.<br />
<br />
<h2>
Challenge: Skills do not Improved</h2>
"Number of Issues been in charge" and "total amount" have been visualized for each designer. In addition, since veteran designers now control on work progress of "designers" as "receptionist", young designers will not commit "no-check delivery" (delivered without checked by anyone).
<br />
<br />
However, intrinsic? measure of value in designing is "quality".
<br />
<br />
With this Business Process as it is, I feel worry that the degree of satisfaction for designs in-house will be going down.
<br />
<br />
Is it impossible to become a Business Process capable of improving skills of the team as a whole a little more? Since we are improving its independency as a "Design request handling process", we would like to think about a mechanism that leads to skill improvement, not just a Business Process for simply to handle numbers of work.
<br />
<br />
<br />
<br />
<div style="text-align: center;">
Example of Business Process to call out [Designing request]
</div>
<div style="text-align: center;">
<a href="http://4.bp.blogspot.com/-Au9-YlWjp_8/WoYyaAF3n6I/AAAAAAAALyQ/96Gb1rhfeO0PxTKk4GxM8m_gW6dgenZ8ACK4BGAYYCw/s1600/20180219_Designing_request-Call_model-en-766053.PNG"><img alt="" border="0" height="116" id="BLOGGER_PHOTO_ID_6522956532575346594" src="https://4.bp.blogspot.com/-Au9-YlWjp_8/WoYyaAF3n6I/AAAAAAAALyQ/96Gb1rhfeO0PxTKk4GxM8m_gW6dgenZ8ACK4BGAYYCw/s640/20180219_Designing_request-Call_model-en-766053.PNG" width="640" /></a></div>
<br />
<div style="text-align: center;">
[Designing request-Reviewing]</div>
<div style="text-align: center;">
<a href="http://4.bp.blogspot.com/-5pVEIZSFz6k/WoYyZVgSpkI/AAAAAAAALyI/T8ZyBfzZ9DgkOpyu8FViQLGTQt7X2nD7ACK4BGAYYCw/s1600/20180219_Designing_request-Reviewing-model-en-763151.png"><img alt="" border="0" height="520" id="BLOGGER_PHOTO_ID_6522956521143445058" src="https://4.bp.blogspot.com/-5pVEIZSFz6k/WoYyZVgSpkI/AAAAAAAALyI/T8ZyBfzZ9DgkOpyu8FViQLGTQt7X2nD7ACK4BGAYYCw/s640/20180219_Designing_request-Reviewing-model-en-763151.png" width="640" /></a></div>
<br />
<a name='more'></a><br />
<h2>
Solution: Review of Questionnaire Format</h2>
"Good or bad in a design" cannot be quantified. Even if the designers in the team discuss on a certain design, they will get only mixed opinions. If negative comments are made about the parts that the creator him/herself is satisfied, it can fall into a barren argument. Only if it is a comment about "the part that the creator him/herself is uncertain", it will be acceptable even a negative opinion.
<br />
<br />
In this business process, a designer describes his/her feeling of reluctance or apprehension about the design, such as for example, "it could be bit brighter", into "3. Preview" to ask opinions to colleagues. (It would be much better to ask "Review, please" verbally.)
<br />
<br />
Colleague who is asked will select from<br />
<br />
<ol>
<li>I agree</li>
<li>Somewhat agree</li>
<li>I don't think so</li>
<li>I disagree</li>
<li>I don't know</li>
</ol>
<br />
<h2>
Discussion: Skill Improvement Environment</h2>
Designers in Marketing department, in Product development department, in Sales department.<br />
<br />
I cannot tell which is better whether "a case where the designer is assigned to each department" or "a case where the design team is independent". Each will have both advantages and disadvantages.
<br />
<br />
However, as a way to proceed a job, it is never desirable for a situation where workers cannot talk to anyone / cannot consult anyone. Particularly about outputs of designing, it is something that will lead to some conversations even just clicking on "Like" on in-house social network (enterprise SNS).
<br />
<br />
Especially if you aim "skill improvement as an organization", it can be said that you should continue to explore such a Business Process environment that allows people with the same skills mutually encourage improving.
<br />
<br />
<div style="text-align: center;">
[Designing Request-Reviewing:"1. Request designing]
</div>
<div style="text-align: center;">
<a href="http://4.bp.blogspot.com/-IqcflziX4So/WoYyagtFOnI/AAAAAAAALyY/meU75BtRJF8oTjzNDoQkbEm7dEQH9Hy7wCK4BGAYYCw/s1600/20180219_Designing_request-Reviewing-form-en-768922.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6522956541329750642" src="https://4.bp.blogspot.com/-IqcflziX4So/WoYyagtFOnI/AAAAAAAALyY/meU75BtRJF8oTjzNDoQkbEm7dEQH9Hy7wCK4BGAYYCw/s640/20180219_Designing_request-Reviewing-form-en-768922.png" width="286" /></a></div>
<br />
<div style="text-align: center;">
<Data Items list>
</div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-2U8-Z5KnsDI/WoYyYlSc_LI/AAAAAAAALyA/L9QiXXzJm9MylNJCsHs2YFRa1wpxEV4HgCK4BGAYYCw/s1600/20180219_Designing_request-Reviewing-data-en-760641.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6522956508200500402" src="https://3.bp.blogspot.com/-2U8-Z5KnsDI/WoYyYlSc_LI/AAAAAAAALyA/L9QiXXzJm9MylNJCsHs2YFRa1wpxEV4HgCK4BGAYYCw/s640/20180219_Designing_request-Reviewing-data-en-760641.png" width="622" /></a></div>
<br />
<hr />
<h4>
<Example of automatic transmission setting in Main process to Sub-process></h4>
<br />
<ul>
<li>key=${sub-process api key}</li>
<li>title=${Title of requested item}</li>
<li>data[1].email=${Requester} <span style="color: #0b5394;">#User type</span></li>
<li>data[6].selects=${Work type} <span style="color: #0b5394;">#Select type:Icons/Illustration/…</span></li>
<li>data[7].selects=${Budget} <span style="color: #0b5394;">#Select type:0-5,000/5,000-10,000/10,000-50,000/…</span></li>
<li>data[8].input=${Desired due date} <span style="color: #0b5394;">#Date type</span></li>
<li>data[9].input=${File format} <span style='color:#0000FF;'>#String type</span></li>
<li>data[10].input=${Purpose of request} <span style="color: #0b5394;">#String type multiple lines</span></li>
<li>data[11].input=${Details of requirement} <span style="background-color: white;"><span style="color: #0b5394;">#String type multiple lines</span></span></li>
<li>data[12].upload: ${Related files} <span style="color: #0b5394;">#File type</span></li>
<li>data[2].input=${URL of Catching Event} <span style="color: #0b5394;">#String type</span></li>
<li>data[3].input=$processInstanceId</li>
<li>data[4].input=${Catching Event Key} <span style="color: #0b5394;">#String type</span></li>
</ul>
<br />
* In order to automatically receive Design report, "URL of Catching Event in connection source Process", "Issue ID of connection source Process", and "Catching Event Key in connecting Process" are mandatory. Other data items are delivered to the extent necessary.<br />
<br />
<h4>
<Data automatically transmitted in Sub-process to Main process></h4>
<br />
<ul>
<li>key=${(Catching Event Key in source Process)} <span style="color: #0b5394;">#main-process api key</span></li>
<li>processInstanceId=${(Issue ID of connection source Process)}</li>
<li>q_designreport=${(Design report)} <span style="color: #0b5394;">#String type multiple lines</span></li>
<li>q_designfiles: ${Deliverable file(to be returned to the connection source Process)} <span style="color: #0b5394;">#File type</span></li>
</ul>
<br />
* String type data item multiple line (field name: q_designreport) that stores "Design report", and File type data item (field name: q_designfiles) that stores "Deliverable file" are needed in the Main process side.<br />
<br />
* For data transmission to the Main process, it is on the premise to use a custom format (field name, e.g. q_designreport) rather than the default parameter format (e.g. data [9]. Input).
<br />
<hr />
[Free download]<br />
<ul>
<li>Business Template: <a href="http://archive.workflow-sample.net/home/en/20180219-Designing_request-Call_en.qar" target="_blank">Designing Request</a></li>
<li>Business Template: <a href="http://archive.workflow-sample.net/home/en/20180219-Designing_request-Reviewing_en.qar" target="_blank">Designing request-Reviewing</a></li>
</ul>
<Similar Models><br />
<ul>
<li><a href="http://en.workflow-sample.net/2017/04/paypal-invoice.html" target="_blank">Episode 529: Making PayPal Operation into Subroutine</a> (2017-04-03)</li>
<li><a href="http://en.workflow-sample.net/2016/12/contract-approval.html" target="_blank">Episode 515: Approval on Contract through Workflow! (Improved version)</a> (2016-12-26)</li>
<li><a href="http://en.workflow-sample.net/2016/03/cartoon-creation.html" target="_blank">Episode 475: Business Process that Finishes "Manga" upon Creating "Scenario"</a> (2016-03-22)</li>
</ul>
<br />
<<Related Articles>><br />
<ul>
<li><a href="https://www.questetra.com/tour/m4/m413/" target="_blank">M413 PROCESS CONNECTION: Setting: Calling Sub-process in the Middle of the Flow, Standing by the Result of It</a></li>
<li><a href="https://www.questetra.com/tour/m2/m226/" target="_blank">M226 AUTO EVENT: Standing by HTTP Request</a></li>
<li><a href="https://www.questetra.com/tour/m2/m210/" target="_blank">M210 ALLOCATION: Designation of Downstream Operator in Upstream Step</a></li>
</ul>
<br />
<br />
[<a href="http://ja.workflow-sample.net/2018/02/process-improvement-saas-vendor-2.html">Japanese Entry (和文記事)]</a>Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-51459009973500412722018-02-13T06:00:00.000-05:002018-02-28T00:33:04.664-05:00Episode 574: Business Improvement in SaaS Vendor Operation (Part 1)<div class="mobile-photo">
<a href="http://1.bp.blogspot.com/-YeIFSn1uEL4/Wn0gteXYu5I/AAAAAAAALwY/BNsIote5cn0VEm3JrykngjY5kn4HsqflACK4BGAYYCw/s1600/574-711641.png"><img alt="" border="0" height="336" id="BLOGGER_PHOTO_ID_6520403801119701906" src="https://1.bp.blogspot.com/-YeIFSn1uEL4/Wn0gteXYu5I/AAAAAAAALwY/BNsIote5cn0VEm3JrykngjY5kn4HsqflACK4BGAYYCw/s640/574-711641.png" width="640" /></a></div>
<div class="mobile-photo">
<br /></div>
<h2>
Operation: Design work</h2>
The work of a design team is extensive.<br />
<br />
There may be small projects such as "changing icons in SaaS products" and adding them, and there may be also major projects such as "interface development of new SaaS functions".<br />
<br />
However... in addition to those, there may be a case where they are requested publishing of a "Customer story article" written by the sales team on the Website, and furthermore, to create a flyer containing the story. Moreover, for an exhibition planned by marketing team, there might occur project of Web contents production, and creation of posters , and so on...<br />
<br />
After all, it can be said that it is "a team that continuously being asked for helping hands?" from the entire company.<br />
<br />
<h2>
Challenge: Efficiency Improve on Work that Occurred Passively</h2>
It is true that the design team is certainly demanded by everybody.<br />
<br />
However, it is inevitable to be said that what they are doing is unobtrusive compared to the fact that the direct division "product development division" and "sales and marketing department" are acting on a daily basis. For example, it is like gift wrapping service counter in a department store. They are keep on giving decorations on outputs of the store as they are asked to do so. And when they notice, "passive attitude" has ingrained on themselves.<br />
<br />
Even if they grumbled that if it was the architectural industry, rather, the "designers will move actively, and the engineering group such as "structural" or "environmental" would be passive, "demands from internal company" won't be gone... First of all, I'd like to consider a way to do this passive job in a handsome manner. (Since, even in accounting, human resource department, or IT department, they are handling these "passive job" brilliantly...)<br />
<br />
<div style="text-align: center;">
Business Template: [Designing Request]</div>
<div style="text-align: center;">
<a href="http://1.bp.blogspot.com/-fYykWvjxZiU/Wn0guzPmAkI/AAAAAAAALw4/5UGW3IfCODUncOMjmBgn-A5A7ypGM5OswCK4BGAYYCw/s1600/20180212-en-717908.png"><img alt="" border="0" height="436" id="BLOGGER_PHOTO_ID_6520403823904031298" src="https://1.bp.blogspot.com/-fYykWvjxZiU/Wn0guzPmAkI/AAAAAAAALw4/5UGW3IfCODUncOMjmBgn-A5A7ypGM5OswCK4BGAYYCw/s640/20180212-en-717908.png" width="640" /></a></div>
<br />
<a name='more'></a><br />
<h2>
Solution: Make the Design Process Independent</h2>
It is inevitable to some extent that indirect departments supporting direct departments become "passive". Also, indirect departmental Steps (swimlanes) are often incorporated into the Business Processes of the direct department.<br />
<br />
However, since the design team himself does not have ownership of the Business Process definition, it tends to occur problems such as<br />
<br />
<ul>
<li>Processes within the design team are not improved</li>
<li>The situation of work load is not recognized</li>
<li>The inputs / outputs of the design process will become disjointed by the work</li>
</ul>
<br />
This Business Process definition, it is not only accepts requests from outside the team but also allows "process linkage" from other Process (cooperation like a subroutine call).<br />
<br />
By defining as an independent Business Process like this, it makes easy to visualize the various tasks that the design team receives.<br />
<br />
(It does not apply to cases where the direct department possesses an "exclusive designer" within the team.)<br />
<br />
<h2>
Discussion: Necessity of Measurement of Performance Results</h2>
A design team is not the only indirect department in a company. There are many other indirect departments within an organization. (It is also referred to as Back office.)<br />
<br />
It is common that teams such as for example, "Legal", or "Human Resources" or "IT system", are independent as an indirect department, even if it is in "an organization of non-flat structure" or "a company with more than a thousand employees". (Other than that, translation team, quality control team, brand management team, BPM team, and so on...)<br />
<br />
However, even though the same indirect departments, the method of Business Process Management differs greatly by Organization which<br />
<br />
<ul>
<li>is not incorporated in daily business of direct department such as "Human Resources department"</li>
<li>tends to be incorporated into the daily work of the direct department, such as "legal team" or "design team"</li>
</ul>
<br />
In other words, if it is a "Human Resource team", it is possible to continue to improve personnel work process groups by themselves with ownership. Whereas, processes such as "Legal check", for example, which is incorporated as one Step of the "Order acceptance process" it will not subject to be improved very much.<br />
<br />
The design team in this case can be said to be a creative team where the measurement of each person's performance is also important. If you need to grow it to a competitive organization, you should probably consider an independent business process that starts with "Request acceptance" from another department.<br />
<br />
<div style="text-align: center;">
[Designing Request:"1. Request designing]</div>
<div style="text-align: center;">
<a href="http://3.bp.blogspot.com/-XvoVFmr6jjg/Wn0gsolNShI/AAAAAAAALwI/bU5paOFH5wMRDoFn0LfWRka-TbBuFwiFACK4BGAYYCw/s1600/20180212-f-en-708568.png"><img alt="" border="0" height="640" id="BLOGGER_PHOTO_ID_6520403786682157586" src="https://3.bp.blogspot.com/-XvoVFmr6jjg/Wn0gsolNShI/AAAAAAAALwI/bU5paOFH5wMRDoFn0LfWRka-TbBuFwiFACK4BGAYYCw/s640/20180212-f-en-708568.png" width="369" /></a></div>
<br />
<div style="text-align: center;">
<Data Items list></div>
<div style="text-align: center;">
<a href="http://2.bp.blogspot.com/-d7F9TjG8qY4/Wn0grHoCDmI/AAAAAAAALvg/kJ6O9mo47zI3k7P-7EqmkkK53jiNtQkPACK4BGAYYCw/s1600/20180212-d-en-702180.png"><img alt="" border="0" height="578" id="BLOGGER_PHOTO_ID_6520403760655765090" src="https://2.bp.blogspot.com/-d7F9TjG8qY4/Wn0grHoCDmI/AAAAAAAALvg/kJ6O9mo47zI3k7P-7EqmkkK53jiNtQkPACK4BGAYYCw/s640/20180212-d-en-702180.png" width="640" /></a></div>
<br />
<br />
[Free download]<br />
<ul>
<li>Business Template: <a href="http://archive.workflow-sample.net/home/en/20180212-Design_Request-en.qar" target="_blank">Designing Request</a></li>
</ul>
<Similar Models><br />
<ul>
<li><a href="http://en.workflow-sample.net/2017/04/paypal-invoice.html">Episode 529: Making PayPal Operation into Subroutine</a> (2016-12-26)</li>
<li><a href="http://en.workflow-sample.net/2016/12/contract-approval.html">Episode 515: Approval on Contract through Workflow! (Improved version)</a> (2017-05-15)</li>
<li><a href="http://en.workflow-sample.net/2016/03/cartoon-creation.html">Episode 475: Business Process that Finishes "Manga" upon Creating "Scenario"</a> (2016-03-22)</li>
</ul>
<<Related Articles>><br />
<ul>
<li><a href="https://www.questetra.com/tour/m4/m413/">M413 PROCESS CONNECTION: Setting: Calling Sub-process in the Middle of the Flow, Standing by the Result of It</a></li>
<li><a href="https://www.questetra.com/tour/m2/m226/">M226 AUTO EVENT: Standing by HTTP Reques</a></li>
<li><a href="https://www.questetra.com/tour/m2/m210/">M210 ALLOCATION: Designation of Downstream Operator in Upstream Step</a></li>
</ul>
<br />
<a href="http://ja.workflow-sample.net/2018/02/process-improvement-saas-vendor-1.html">[Japanese Entry (和文記事)]</a>Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.comtag:blogger.com,1999:blog-5566342705207961669.post-68851612914716363592018-02-05T06:00:00.001-05:002018-02-09T01:24:16.227-05:00Episode 573: Business Improvement in Website Operation (Part 3)<div class="separator" style="clear: both; text-align: center;">
<a href="https://4.bp.blogspot.com/-TsgxHkoEVdk/WnQmmqhRK2I/AAAAAAAACYM/35c3bMeMcVYytRtVWi3yJ3dg_bYTy8_CgCLcBGAs/s1600/article-idea-acceptance.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="630" data-original-width="1200" height="336" src="https://4.bp.blogspot.com/-TsgxHkoEVdk/WnQmmqhRK2I/AAAAAAAACYM/35c3bMeMcVYytRtVWi3yJ3dg_bYTy8_CgCLcBGAs/s640/article-idea-acceptance.png" width="640" /></a></div>
<br />
<h3>
Operation: Web Article Production</h3>
I changed the Workflow of the article writing. (Reference: <a href="http://en.workflow-sample.net/2018/01/process-improvement-webmedia1.html">Episode 571: Business Improvement in Website Operation (Part 1)</a>, <a href="http://en.workflow-sample.net/2018/01/process-improvement-webmedia2.html">Episode 572: Business Improvement in Website Operation (Part 2)</a>)<br />
<br />
It has become a flow leading to the skill improvement of "writers" as well as improving the quality of "articles" by this, I suppose. <br />
<br />
In any case, a series of "article creation flow", starting with "Setting of provisional title" and leading to "output of web article", came to be smooth. It can be said that useless communication such as "going to check progress" or "going to ask for reviews" is completely eradicated. <br />
<ul>
<li>Editor-in-chief: Launch the planning such as seasonal series </li>
<li>Editors: Determine provisional titles of individual articles </li>
<li>Writers: Write articles </li>
</ul>
It would be better to be expressed that the editor-in-chief, editors, writers have become able to concentrate in their own original role. (Though "rework" or "educational guidance" are not completely eliminated...) <br />
<br />
<h3>
Challenge: Problem of Out of idea </h3>
On the other hand, it has become to be discussed on the quality of "provisional title" which is an input to "article production flow". <br />
<br />
That is, (though this might be an everlasting challenge for those owned media,) there would be a case where a mood which they are running out of idea for "provisional titles filled the atmosphere... such as "recently wrote a similar article", or "nobody would like to read"... <br />
<br />
In this occasion, I would like to make it being able to suggest from the entire company about the ideas of articles (provisional titles) and plans of series. <br />
<br />
If there are plenty of ideas, they will be a help for editors and the editor-in chief. And the quality of setting "provisional title" should increase. <br />
<br />
<div style="text-align: center;">
[Article Idea Acceptance] </div>
<div class="mobile-photo" style="text-align: center;">
<a href="http://2.bp.blogspot.com/-aE7_Lyd06is/WnQKJPV_iqI/AAAAAAAALuM/7eiMnkVKYv0Z2yiWkUg_ne_XCv5dR-EnQCK4BGAYYCw/s1600/20180205-en-710201.png"><img alt="" border="0" id="BLOGGER_PHOTO_ID_6517845714565827234" src="https://2.bp.blogspot.com/-aE7_Lyd06is/WnQKJPV_iqI/AAAAAAAALuM/7eiMnkVKYv0Z2yiWkUg_ne_XCv5dR-EnQCK4BGAYYCw/s1600/20180205-en-710201.png" width="500" /></a></div>
<br />
<a name='more'></a><br />
<br />
<h3>
Solution: Suggestion Box</h3>
The Business Process for accepting ideas is not operated than you expect. <br />
<br />
"Responsibility in charge of planning" in the organization is responsible for the "most upstream step". In other words, it is a job that must continue to output such as "five projects a week" or "10 planning a month" without any inputs. <br />
<br />
And whenever you stand on the "outgoing side" every day, you forget to become a "receiving side". It may be the same trend (symptoms) like such as a school teacher loses the opportunity to listen to the students' voices, or a product vendor loses chances for listening to the user's voice. <br />
<br />
A system to continue to produce "articles desired by readers" should be maintained by keeping everybody's eyes open as an organization, to ideas such as articles related with current news, or popular article of other company's media, and so on... <br />
<br />
<h3>
Discussion: Process to be Started even by Email</h3>
However, there may be some opinion that "it is only necessary to send by mailing list or chat as appropriate" about the "suggestion box-like business process" that accepts ideas. Certainly, if you heard that "flow ideas into a Workflow", you may get an impression little bit troublesome. <br />
<br />
However, considering about points such as <br />
<ul>
<li>Ideas in the past have been all recorded </li>
<li>The thoughts of the "planner" on each idea have been recorded </li>
<li>Staffs in other sections or newly joined are also able to refer to the past records </li>
</ul>
you should consider a method of defining a Business Process properly and flowing it to the Workflow system. <br />
<br />
The Business Process definition exemplified here is excellent in that it is devised so that ideas can be sent not only in the "input screen (Web browser)" of the Workflow system but also by "email transmission". <br />
<br />
<div style="text-align: center;">
[Article Idea Acceptance:"1. Submit" idea screen] </div>
<div class="mobile-photo" style="text-align: center;">
<a href="http://1.bp.blogspot.com/-C8B3e4IR5H0/WnQKLJAGlSI/AAAAAAAALu0/TrRxeT5nZZAQ2_na0N6Q1ycj4vTKT4AGACK4BGAYYCw/s1600/20180205-f-en-718517.png"><img alt="" border="0" id="BLOGGER_PHOTO_ID_6517845747223139618" src="https://1.bp.blogspot.com/-C8B3e4IR5H0/WnQKLJAGlSI/AAAAAAAALu0/TrRxeT5nZZAQ2_na0N6Q1ycj4vTKT4AGACK4BGAYYCw/s1600/20180205-f-en-718517.png" width="400" /></a></div>
<br />
<div style="text-align: center;">
<Data Items list> </div>
<div class="mobile-photo" style="text-align: center;">
<a href="http://4.bp.blogspot.com/-mp-JUCiHXBA/WnQKJprjkqI/AAAAAAAALuc/xm13B1t_H9USDR-emeivnSOI0wk-tXPAACK4BGAYYCw/s1600/20180205-d-en-713117.png"><img alt="" border="0" id="BLOGGER_PHOTO_ID_6517845721635590818" src="https://4.bp.blogspot.com/-mp-JUCiHXBA/WnQKJprjkqI/AAAAAAAALuc/xm13B1t_H9USDR-emeivnSOI0wk-tXPAACK4BGAYYCw/s1600/20180205-d-en-713117.png" width="500" /></a></div>
<br />
<br />
[Free download] <br />
<ul>
<li>Business Template: <a href="http://archive.workflow-sample.net/home/en/20180205-Article_Idea_Acceptance-en.qar" target="_blank">Article Idea Acceptance</a></li>
</ul>
<Similar Models><br />
<ul>
<li><a href="http://en.workflow-sample.net/2017/09/kaizen-suggestion.html">Episode 552: "Idea Soliciting" is Important for Work Style Reformation</a> (2017-09-11)</li>
<li><a href="http://en.workflow-sample.net/2017/05/attendance-report-improve.html">Episode 535: True Work Style Reformation is to Improve the System Continuously</a> (2017-05-15)</li>
<li><a href="http://en.workflow-sample.net/2017/01/mail-start.html">Episode 516: Method of Starting Workflow by "Email"</a> (2017-01-02)</li>
</ul>
<<Related Articles>><br />
<ul>
<li><a href="https://www.questetra.com/tour/m2/m224/">M224 AUTO EVENT: Auto Sending of Email with Business data Inserted</a></li>
<li><a href="https://www.questetra.com/tour/m4/m401/">M401 BUSINESS FLOW: Setting: Separate the Steps of Application from Reworking for the sake of Easy Monitoring</a></li>
<li><a href="https://www.questetra.com/tour/m4/m415/">M415 AUTOMATED STEP: Adding an Auto-Step to be Used for Business Process Definition</a></li>
<li><a href="https://www.questetra.com/tour/m4/m415/addon-converter-email2quser/">Converter (Email to Quser)</a> (Add-on commentary)</li>
</ul>
<br />
<a href="http://ja.workflow-sample.net/2018/02/process-improvement-webmedia3.html">[Japanese Entry (和文記事)]</a>Questetra INFOhttp://www.blogger.com/profile/14774769970509238666noreply@blogger.com