Oooh! Why can't I attach files onto the Workflow?

Such a Workflow is totally out of date! Workflows have being advanced day by day. Not only basic data such as 'String type', 'Numeric type', 'Date type', 'Time type', it is also available those data type such as,
  • 'Select type', which uses external list.
  • 'Select type', which choices are configured in the upstream.
  • 'Table type', which makes variety of data into a table.
  • 'Discussion type' which data is added with timestamps.

Also BPM: Business Process Management which is for improving business flow, variety of data type can be set in 'Data set' that flows on Workflow. At least Questetra BPM Suite can do it...

See; Modeling: Available Data Types (Questetra/tour/reference)

And now we'd like to consider required data sets in "Contract Processing".

[Contract Processing flow]

The Contract Processing, actually is a Workflow which contains unpredictable numbers of files. Agreement, specification documents, Notices, etc... Have no time for encasing those files in a ZIP file every time. In that point of view, 'File type' which can be attached any number of files is desirable.

And to record the process of negotiation and advice between Legal personnel and Sales personnel, we'd definitely want a "Discussion type" that is automatically records the outgoing comments and time stamp.

Incidentally, in this work flow definition, the conversation exchange between Legal personnel [2. Notes for negotiation/approval] and Sales personnel [3. Contract negotiations Report] goes back and forth. And also, the flow splits into [2a. Review and comment of the draft] by Sales Leader. To achieve these, advanced Workflow or sophisticated Business Process Management is required.

[Contract Processing flow [2. Notes for negotiation/approval] screen]

< Similar Models >

<< Related Articles >>

To catch up with the flow of business for up to "orders" from the "quote".

-To check which quote is under the judgment of 'Orders / Lost' anytime
-To tell necessary and sufficient information automatically to relating sections without any leakage when got orders.

First of all, 'Sharing current information' is prior among varieties of affairs in Sales section. In the following Workflow definition, the project management of sales team is defined in a very simple Workflow. It exactly is a Simple SFA. I want to note here is, the daily business report can not be continued if it's not simple.

This Workflow begins with [1. Project Opening report] by a sales personnel. Right after the registration of Project Opening, a Task of [1a. Advice/ Strategy] is allocated to the Sales leader clearly.

[Sales-Quote/Orders share flow]

After that, the sales personnel adds progress when the status changes in his project such as submitting quote or visiting, onto Discussion type data at Task [2. Quote Submitting/ Visiting], then [save]. If there is something should be shared, check the 'In negotiation' flag then [Finish]. In that case, a 'Project progress share email' is automatically sent to members of the team.

In addition, when orders or Lost became final and conclusive, the sales personnel click to select [Status] flag, then 'Finish' task of[2. Quote Submitting/ Visiting]. Doing this, a "I got the Order! email" is sent to members of the team automatically.
(Only the supervisor should know data for analysis on Lost. That is, it's better to be set that 'Case lost email' be sent only to the Leader.)

There are Workflows which end a series of processes with totally 'unmanned'.

"Unmanned Workflow", it is a Workflow that only when an error occurs human takes part in it. For example, a Workflow that (1) Accepting requests for "Free Account" on the Web site, and (2) Setting new accounts in the system automatically, then (3) Sending a 'Welcome mail' to the applicant. That is one of 'unmanned Workflow'.

The following is an unmanned Workflow that takes a role of 'Database', receiving sales data from various business processes. Only sales data out of all Claim flow is sent, and sales data of all business is aggregated.

[Unmanned Sales Data flow]

Ease the Monthly Billing

Monday, February 6, 2012
Can you define a 'Workflow'?
Somehow, it often seems "IT knowledge" to be required, but it isn't. Rather, "Business knowledge" is indispensable.

'Billing flow', for example. It is exactly what the core operation, and it's not easy to list up all the processing steps.
1. Complement the series of procedures from 'Delivery / Shipment' of merchandise??
2. Complement the series of procedures from 'Order Report' by salesperson?
3. Complement the series of procedures from 'Query / Leads' ?
It is a hassle just to set 'Workflow range considering to be easy its operation'. And of course, the 'Workflow To Be' depends on the Business line, the organizational size, or organizational culture.

In this article, we would like to take a look at a Billing flow for Cloud services business and Rental business, etc. It is also assumed monthly repeat cases on a contract basis.

[Billing flow - Cloud service]