Wiki: CONFIGURATION-WF

This is version . It is not the current version, and thus it cannot be edited.

Back to current version Restore this version

The concepts of workflow require that users understand the principals of the application and have the knowledge and capabilities to write UserCalcs. It is also important to recognize the needs of your business in order to determine if workflow is applicable. It may be useful to have SQL knowledge to write Completion Clauses

The set up required to integrate workflow is not complex. Basically, there are two screens required for set up, they are: Define Workflow Actions IMWA and Define User Calculations IMUC. The difficulty arises mainly from the complexity of the UserCalc and the completion clause. However, not all workflow actions are complicated and it depends on a client's business requirements.

Workflow triggers are initiated when a record is inserted, updated or deleted from the database. Each table that is enabled for workflow will have a data base trigger configured.

Workflow Action#

A workflow action is the result of a key event. Some key events can include a salary/wage increase or hiring/ terminating an employee. These events require specific actions to occur, thereby driving the workflow process.

UserCalcs and Workflow#

This section should only act as a supplemental aid to the already existing User Calculations section. Its intent is to explain some new features that have been developed as a result of the integration of workflow into system. Please reference the User Calculations section for more detail on the other UserCalc items.

With the integration of workflow into the system, UserCalcs have the ability, in addition to their previous functionality, to allow for workflow action events to occur under specific conditions. Examples of such events include: issuing an email, alerting users of specific tasks and taking the user to that particular screen to complete the task. Workflow action events are only processed through UserCalcs.

Purpose of UserCalcs#

A UserCalc is a set of instructions, defined by the user, which trigger specific actions or operations to take place.

They are a powerful feature that allows for customization of the application to a high degree. UserCalcs can perform various operations, such as arithmetic calculations, comparisons of different items, date checks and calculations, issue warning messages and workflow action events.

UserCalcs can be simple or quite complex.

Workflow#

The activation of a workflow trigger results in the initiation of a UserCalc. Once the UserCalc is initiated, the workflow action events are called from within the UserCalc.

How to Plan a Workflow UserCalc
UserCalc Conventions
UserCalc TypesWorkflow is only concerned with Calculation types.

Define User Calcs#

The other component of workflow requires setting up the UserCalc to incorporate the action event created in IMWA. The integration of workflow required some additional functionality that was not previously available to UserCalcs. This section should be used as a supplemental aid to the User Calculations manual and is not to be used in place of it. Please refer to the User Calculations section for a more thorough explanation of UserCalcs and their functionality.

Define Workflow UserCalc
- Lines Tab

Publish User Calculations#

The putting of UserCalcs into production is controlled in Publish User Calculations IMUCA. The administration of UserCalcs also involves an expanded knowledge of the status of UserCalcs. Please refer to the User Calculations section for a more detailed explanation. Once a workflow UserCalc has been put "In Production" to stop it from firing you not only have to "UNPUBLISH" it but also then set its status back to "Under Construction".

Publishing UserCalcs

View Execution Logs & Details #

Required Set Up#

IMST Setup for Workflow

Functions for Forecasting and Costing#

Here are some other points or information to help make your use of workflow a success. Once a Workflow UserCalc has been put "In Production", to stop it from firing you not only have to "UNPUBLISH" it but also then you need to set its status back to be "Under Construction".