Oracle Workflow Database Table - Essay Example

Other application Of Oracle, Which means that it also utilizes database tables as the basis Of its operation. Behind its very pleasant and user-friendly GIG_J, It’S the database tables Which Store every piece of information regarding the attributes, functions, process, messages you create while designing a workflow. If you really want to know workflow and discover owe it works, you have to understand Its table structures.

We Will Write A Custom Essay Sample On

For Only $13.90/page

order now

In this article, I have covered the tables which got affected, when you create or modify a workflow process. However It doesn’t include the tables which capture information at run time when you run a workflow. I have taken the POP Approval workflow (VAPOR) for example purpose. 11 The table contains one record for each item_type created. The eight character name of the Item_type represents the “Internal Name” of the Item. It also functions as the primary key for this table.

Some key columns are: NAME: It Is a mandatory field. It represents the internal name of the Item type. PROTECT_LEVEL: Level at which the data Is protected. A mandatory field. CUSTOM_LEVEL: Level of user who last updated the row. Again a mandatory field. WFM_SELECTOR: It stores the name of the PUS’S procedure which implements selector function. This is an optional field. PERSISTENCE_TYPE: Indicates whether item type is temporary or permanent. PERSISTENCE_DAYS: Number of days until purge if persistence is temporary.

Workflow Item Type Display Name and description can be found in WFM_ITEM_TYPES _ TTL table. Also check the SELECT FROM WHERE NAME=’VAPOR; FROM WHERE NAME-=APPROVE; SELECT FROM WHERE NAME-=APPROVE; This table stores definitions of attributes associated with a process. The entries in this table correspond the ‘Attributes” subheading in the workflow Shoulder. An Item attribute works like a variable which can hold values that are specific to the process instance or which may change at run time. Some key columns are: ITEM_TYPE:

Internal name for the Item type that owns the attribute. A mandatory field. NAME: Internal name to the attribute. A mandatory titled. SEQUENCE: Order of the attribute within the message TYPE: Each item attribute is assigned a database. Such as ‘Character, “Number”, or “Date. There are three fields to hold a default value. But only one of them will be populated for any item attribute. Depending upon the database. For example. If you create an item attribute with a database of “Number.