Sample topic workflow configuration
A sample topic workflow configuration and sample topic are provided with Oracle Empirica Signal.
Note:
The Sample Topic Workflow Configuration itself should not be edited.Use the information below as a guide when designing a new topic workflow configuration.
In addition to this sample topic workflow configuration, when you install Oracle Empirica Signal, a single topic with an action is also installed. You can see it on the Topic Management page.
Basic configuration options
When you edit a topic workflow configuration you set these configuration options:
Option | Definition |
---|---|
Name |
Sample Topic Workflow Configuration |
Description |
Sample Topic Workflow Configuration |
Allow topic to be visible to |
( ) One and only one work team (o) Zero, one or more work teams |
Allow topic to be linked to |
(o) Topics in any state ( ) Topics in final state |
Allow addition of comments to |
|x| Topics |x| Attachments |x| Actions |
Allow sources of attachments |
|x| Application Data |x| External URL |x| External Document |x| Note |
Allow topic state closure only when all actions are completed |
| | (cleared) |
Allow action state closure only when attachments or comments are provided for action |
| | (cleared) |
Field definitions: topics
When you view existing fields, the Context column indicates whether a given field applies to topics, attachments, actions, or possibly to several of these contexts.
The sample topic workflow configuration defines the following fields for topics:
Column Name | Display Name | Format | Filter Field |
---|---|---|---|
TOPIC_NAME |
Topic name |
String |
No |
TOPIC_DESCRIPTION |
Topic description |
String |
No |
CURRENT_STATE_ID |
Current state |
Integer |
Yes |
STATE_CHANGE_REASON |
Reason for change |
String |
No |
ASSIGNED_TO_USER_ID |
Assigned to |
Integer |
Yes |
SEARCH_KEYWORDS |
Keywords |
String |
Yes |
RESOLUTION |
Resolution |
String |
No |
RESOLUTION_DATE |
Resolution date |
Date |
No |
(This table presents a subset of the different attributes that can be set when you add or edit a field.)
Field definitions: actions
The sample topic workflow configuration includes the following fields for actions:
Column Name | Display Name | Format | Filter Field |
---|---|---|---|
ACTION_NAME |
Action name |
String |
No |
ACTION_DESCRIPTION |
Action description |
String |
No |
ACTION_STATE_ID |
Action state |
Integer |
Yes |
ASSIGNED_TO_USER_ID |
Assigned to |
Integer |
Yes |
START_DATE_$ORCL |
Start date |
Date |
No |
PLANNED_COMPL_DATE |
Planned completion date |
Date |
No |
ACTUAL_COMPL_DATE |
Actual completion date |
Date |
No |
ACTION_TYPE_ID_$ORCL |
Action type |
Integer |
Yes |
Field definitions: attachments
The sample topic workflow configuration includes the following fields for attachments:
Column Name | Display Name | Format | Filter Field |
---|---|---|---|
NAME |
Attachment name |
String |
No |
DESCRIPTION |
Attachment description |
String |
No |
URL_ADDRESS |
URL address |
String |
No |
FILE_NAME |
File name |
String |
No |
Topic states
The sample topic workflow configuration defines the following workflow states for topics:
Name | Description | Initial State | Final State | Next Possible States |
---|---|---|---|---|
Init |
Initial state |
Yes |
No |
Assigned, Closed, Escalated |
Assigned |
Actively being reviewed |
No |
No |
Closed, Escalated |
Escalated |
Warrants further attention |
No |
No |
Assigned, Closed |
Closed |
No further action needed or expected |
No |
Yes |
Assigned |
Topic field accessibility
The sample topic workflow configuration defines the level of user access to topic fields for a topic in each workflow state as follows:
Topic Field Column Name | Init | Assigned | Escalated | Closed |
---|---|---|---|---|
TOPIC_NAME |
Required |
Required |
Required |
Required |
TOPIC_DESCRIPTION |
Editable |
Editable |
Editable |
Editable |
CURRENT_STATE_ID |
Editable |
Editable |
Editable |
Editable |
STATE_CHANGE_REASON |
-- (Hidden) |
Required |
Required |
Required |
ASSIGNED_TO_USER_ID |
Editable |
Required |
Required |
Required |
SEARCH_KEYWORDS |
Editable |
Editable |
Editable |
Editable |
RESOLUTION |
-- (Hidden) |
-- (Hidden) |
-- (Hidden) |
Required |
RESOLUTION_DATE |
-- (Hidden) |
-- (Hidden) |
-- (Hidden) |
Required |
Action states
The sample topic workflow configuration defines the following workflow states for actions:
Name | Description | Initial State | Final State | Next Possible Action States |
---|---|---|---|---|
Init |
Initial state |
Yes |
No |
Closed |
Closed |
Action completed |
No |
Yes |
|
Planned |
Planned state |
No |
No |
Init |
Action field accessibility
The sample topic workflow configuration defines the level of user access to action fields for an action in each workflow state as follows:
Action Field Column Name | Planned | Init | Closed |
---|---|---|---|
ACTION_TYPE_ID_$ORCL |
Required |
Required |
Required |
ACTION_NAME |
Required |
Required |
Required |
ACTION_DESCRIPTION |
Editable |
Editable |
Editable |
ACTION_STATE_ID |
Editable |
Editable |
Editable |
START_DATE_$ORCL |
Editable |
Editable |
Editable |
ASSIGNED_TO_USER_ID |
Editable |
Editable |
Editable |
PLANNED_COMPL_DATE |
Editable |
Editable |
Editable |
ACTUAL_COMPL_DATE |
Editable |
Editable |
Editable |
Attachment field accessibility
The sample topic workflow configuration defines the accessibility of attachment fields for each type of attachment as follows:
Field Name | External URL | Oracle Empirica Signal Result | External Document | Note |
---|---|---|---|---|
NAME |
Required |
Required |
Required |
Required |
DESCRIPTION |
Editable |
Editable |
Editable |
Editable |
URL_ADDRESS |
Required |
-- (Hidden) |
-- (Hidden) |
-- (Hidden) |
FILE_NAME |
-- (Hidden) |
-- (Hidden) |
Required |
-- (Hidden) |
Parent topic: Preconfigured topic workflow configurations