Components of Oracle workflow process:
Item Type
Process
Attributes
Notifications.
Messages
Functions
Events
Lookup Types
Transition
Data Store
Item Type: Unique Name of the Workflow. (extension of workflow is .wf)
Grouping of workflow components into high level category.
Its like a parent.
Process:
its a picturial/graphical reprsentation of workflow process.
collection of activities and relation between activities.
Two types of process:
(i) runnable process:
A process which can be passed as a parameter to the workflow engine.
example 2 processes in the workflow, (permanent emp/ temp emp)
when perm emp applies perm emp process should be triggered.
temp emp applies temp emp process should be triggered.
(ii) non-runnable process:
Its only a processes, but not passing parameters in it.
calling sub processes ..
x, y two processes.
x by passing parameter (runnable process)
x calls y in the workflow process (y as a non-runnable process).
Attributes:
Its a global variable. to store the values.
And It is used to transfer the exchange between workflow and database is done by Attributes.
Types of Attributes:
10 types available.
10 types of values can be stored . (char, number, date...etc)
Notifications:
Its a non-automated unit of work, which sends electronic information to receipent roles.
2 types of notifications:
FYI: for your information notification type. (only sending attributes, no response)
Todo or FYA For your actions notification type. (sending, response)
send atributes: leave type, no of days.. emp name...
respond attribures; approve/reject
1 workflow can have n number of notifications.
Messages:
That information of leave type, emp name ... dertails cannot be taken in notifications.
Message is container of information, which carries the notification.
Message 2 paarts
Subject :
Body: Actual information of the msg.
two types of bodies:
Text body.
HTML Body.
Relation between notification and message.
One notification can be attached to (access) only one message.
One msg can be attached to n number of notifications.
Functions:
Its a automated unit of work, which executes automatically.
(executing pl/sql procedure in the database from the workflow using funtions)
In the workflow Function we call the procedures from the database.
In the workflow Function we cannot call the functions or pl/sql from the database.
for every function in the workflow, u need to specify the cost (how much time i need to execute the procedure of database).
Events:
Business Event means within the oracle applciation base on the event, (creating po, updating po) do something.
we can list all the event activities with the current item type.
Events can be raised by the form (updating po)
events can be raised during notification (shortage of stock after so is approved)
raise , receive or sent are 3 things done by the events.
Lookup Types:
Static list of values in the workflow.
Have to create manually the values in the lookup type in the worklow , then attach the lookup type in the workflow.
Transition:
used to join two independent activities.
It is denoted with the arrow symbol.
Data Store:
Which we are going to storesor process definition (item type) is called data store.
Data store is a database or can be a flat file.
Storing in the database is called a database.
stroring in the flat file in desktop.
Directory Services:
set of views (wf_users,wf_roles,wf_user_roles)
Using performer as afzal (user).
If storing in the attributes (as a variable), it dont use the directory services.
If not using directly the directory services (of class 1), it uses the directory servcies.
Workflow Arctiture:
1. Workflow builder
while installing workflow builder Workflow definition files.
e:/ora_home1/wf/data/us/
path.
Workflow definition files has have pre defined components, like start and end.
(same as library files attaching during the custom form builder)
Workflow loader:
download/upload
2.
Oracle sever: (database)
Workflow Engine..
In the architecture we can see two way process, of flow..
Item Type
Process
Attributes
Notifications.
Messages
Functions
Events
Lookup Types
Transition
Data Store
Item Type: Unique Name of the Workflow. (extension of workflow is .wf)
Grouping of workflow components into high level category.
Its like a parent.
Process:
its a picturial/graphical reprsentation of workflow process.
collection of activities and relation between activities.
Two types of process:
(i) runnable process:
A process which can be passed as a parameter to the workflow engine.
example 2 processes in the workflow, (permanent emp/ temp emp)
when perm emp applies perm emp process should be triggered.
temp emp applies temp emp process should be triggered.
(ii) non-runnable process:
Its only a processes, but not passing parameters in it.
calling sub processes ..
x, y two processes.
x by passing parameter (runnable process)
x calls y in the workflow process (y as a non-runnable process).
Attributes:
Its a global variable. to store the values.
And It is used to transfer the exchange between workflow and database is done by Attributes.
Types of Attributes:
10 types available.
10 types of values can be stored . (char, number, date...etc)
Notifications:
Its a non-automated unit of work, which sends electronic information to receipent roles.
2 types of notifications:
FYI: for your information notification type. (only sending attributes, no response)
Todo or FYA For your actions notification type. (sending, response)
send atributes: leave type, no of days.. emp name...
respond attribures; approve/reject
1 workflow can have n number of notifications.
Messages:
That information of leave type, emp name ... dertails cannot be taken in notifications.
Message is container of information, which carries the notification.
Message 2 paarts
Subject :
Body: Actual information of the msg.
two types of bodies:
Text body.
HTML Body.
Relation between notification and message.
One notification can be attached to (access) only one message.
One msg can be attached to n number of notifications.
Functions:
Its a automated unit of work, which executes automatically.
(executing pl/sql procedure in the database from the workflow using funtions)
In the workflow Function we call the procedures from the database.
In the workflow Function we cannot call the functions or pl/sql from the database.
for every function in the workflow, u need to specify the cost (how much time i need to execute the procedure of database).
Events:
Business Event means within the oracle applciation base on the event, (creating po, updating po) do something.
we can list all the event activities with the current item type.
Events can be raised by the form (updating po)
events can be raised during notification (shortage of stock after so is approved)
raise , receive or sent are 3 things done by the events.
Lookup Types:
Static list of values in the workflow.
Have to create manually the values in the lookup type in the worklow , then attach the lookup type in the workflow.
Transition:
used to join two independent activities.
It is denoted with the arrow symbol.
Data Store:
Which we are going to storesor process definition (item type) is called data store.
Data store is a database or can be a flat file.
Storing in the database is called a database.
stroring in the flat file in desktop.
Directory Services:
set of views (wf_users,wf_roles,wf_user_roles)
Using performer as afzal (user).
If storing in the attributes (as a variable), it dont use the directory services.
If not using directly the directory services (of class 1), it uses the directory servcies.
Workflow Arctiture:
1. Workflow builder
while installing workflow builder Workflow definition files.
e:/ora_home1/wf/data/us/
path.
Workflow definition files has have pre defined components, like start and end.
(same as library files attaching during the custom form builder)
Workflow loader:
download/upload
2.
Oracle sever: (database)
Workflow Engine..
In the architecture we can see two way process, of flow..
No comments:
Post a Comment