In that case, it may become uncomfortable situation if the workflow was too automated.
It costs much when "Free Trial" was actually mailed to the address which development stuff entered for testing.
Expand "Making Customer List That Tells You How Good, Out From "Free Trial" to split the flow for "Test". In the following workflow model, automatic processing of publishing accounts is not performed when when you input [Applicant Name] started string of "test"
Similar:
- Automate From Acceptance To Issue On Trial Account
- "Free Trial Account" Issuance Automated And Unmanned
- Making Customer List That Tells You How Good, Out From "Free Trial"
<Tasks>
0. Test Check, 1. Application Info, 2. Manual Issue Account, 3. Verification, 4. Lead Info, 5. Sales Phone Result
[Trial Account Issue-Automatic Issue:[0. Test Check] screen]
<Items>
- Title<<Company Name>>
- Name(string)
- Company(string)
- Email Address(string)
- Phone Number(string)
- Other Info(string: text box 3lines)
- Ignore?(select:yes/no)
- Expectation(select:Expected/Ignore)
- Issued Account(string)
- Expectation Mark(1-10)(numeric)
- Correspondent(discussion)
When the condition of "[Applicant Name] is started with string of [test]" is true, it flows into the Task [0. Test Check] and account issue is not processed. If you want to test [Account Issue Process] or [Complete Notification], it can be considered like the following Workflow model to split at [3. Verification]. (It seems like no different from selecting [Ignore] at [Expectation], but can be recorded explicitly test input.)
<Tasks>
0. Test Check, 1. Application Info, 2. Manual Issue Account, 3. Verification, 4. Lead Info, 5. Sales Phone Result
