• It is possible to define to which file card the flow belongs,
• Flow can be deleted if it is not used or old version, and can be save as a new version,
• While created, flow can just be read, changed or for file card or additional structure, properties can be selected. This option can be done for document screen as well. "Old versioned flows cannot be changed; they can only be read or copied.
• Prepared flow is published. Until this process, flow stays as draft, and seen in no list.
• There is a structure where warning of missing sections is set out.

• There is a log mechanism for each flow design, and all changes done on flow can be traced from here.
• Each flow consists of steps. These steps are connected to each other. Moves of flow can be directed by connection of selections to step or steps.
• Each flow can only have one start, but more than one end.
• File card can automatically enter flow at each time it is recorded, changed according to change of a field or its value. In accordance wit file card record (new record, record changed, record added), it may automatically enter the flow.
• It can be specified to which file card each flow belongs.
• Flow can be canceled by system administrator, authorized user, or carried to another step.
• There is an option for a flow to run to least resting flow while it is directed to next user, group, or role (round robin). If wanted, weight of flow can be specified according to this.
• There is an option for file card record to go to more than one flow or not. This can be specified in flow properties.
• Users having the right to create a flow, who are not managers or administrators can assign people responsible for flow among those having file card rights. Flow designers can authorize related users, roles or groups.
• Messaging at automatic steps, sending mail (if there is), and all kinds of moves together with information can be realized by system user.
• If file card design is included in flow, and related field is used, it cannot be changed, and user is warned on this.
• If a conditional step is used, related field cannot be deleted in file card design.
• If file or record is included in a flow, it cannot be included in the same flow again. This is checked in automatic add-ins to flow.
• If file card record is included in more than one flow (different flows), just read only option is selectable for record. That is, if a document can be added according to A flow, and it is read only according to B flow, in that case file card record is just read only.

Gereal Features of Steps, and Options:

• Steps stand for tasks, and processes at one-step.
• Steps enable flows to be directed at circulating places according to specific option.
• When file card record gets into flow, and arrives at step, warning system (e-mail, message) can warn related users, groups, or roles.
• It can be specified whether a file card record can pass to next step or not by approval of one or all of one or more than one user from whom it has left.
• One step can be connected to more than one step. No step is independent.
• Except start, and end, each step has at least one entrance, and one exit. Only start step cannot have an entrance, and end step cannot have exit.
• Options step is used to get connected in more than one step.
• Options have father-child relation. One option can have only one father, and minimum one child relation.
• One-step can be connected to one or more options. However, it cannot be connected to itself, and to the start. End cannot connect to any other step.
• At design, automatic directing can be done over values of file card fields. This enables more than one field to be used in directing. Fields are connected to each other with AND.
• In order to time out warning system at steps, it is possible to direct to another step with another option.
• Time out for steps can be specified as days, hours, and minutes.
• Users can be given the right to put off task at time out. User has the ability to postpone according to this option.
• In case that condition is provided, flow goes to one-step. It goes to another step in case the condition is not provided.
• Flow will have proxy property. It may be directed to proxy user between specified dates.
• Distribution has been provided among group, department, and roles by Round-Robin system.