Information Technology Reference
In-Depth Information
With this rich feature set, FSM fundamentally changes the approach for the config-
uration of an environment. It makes configurations portable and allows rapid deploy-
ments.
FSM components
FSM has a set of foundational components as part of its architecture. These com-
ponents are grouped together to provide the various features of FSM. The primary
component of FSM is the Business Object .
A business object is any foundational entity that is part of an organization's process.
These can be both physical and conceptual entities. Examples of business objects
are employee, invoice, order, item, and ledger.
These business objects have activities that can be performed on them. The state
of a business object would change based on the activity that is executed. The FSM
refers to these activities as Tasks . The relationship between a business object and
a task is shown in the following diagram:
Tasks are classified into the following two types:
Setup Tasks : These tasks are performed during the configuration of the ap-
plication and are usually one-time events that need to be performed to con-
figure the application. Examples of setup tasks are assigning reporting cur-
rency and creating item structure, just to name a few important tasks.
Tasks : These are transactional activities that are performed on a regular
basis and are the standard functions that would be performed on a business
object.
Setup tasks are not performed in isolation. They are usually part of a sequence of
steps that need to be performed in a predefined order. The FSM provides Task Lists
that group setup tasks and ensure that they are interlocked correctly.
Search WWH ::




Custom Search