Component
Definition
Functions that can be arranged on a user interface for processing business transactions, or that are executed automatically by the system in the background.
Use
You want to process a business transaction from a
specific
user interface.
You want to identify a customer who calls your company’s call center in the
Business Partner Search
, display their bank details, contacts, campaigns, orders, and complaints in the
navigation area
, and enter an ad or subscription order, end the call, enter data on the contact, end the contact and accept a new contact from the queue in the
Application Area
.
Structure
A component has a component or configuration profile that describes the specification of the component.
The components are subdivided into visible and invisible components:
A visible component is displayed as a subscreen in a screen area (slot) in the framework.
An invisible component contains a background function that does not require its own screen area (slot).
Integration
The components are assigned to a framework and interact with each other.
See also: Framework
Assigning Visible Components
You can assign the visible components to an L-shaped framework as follows:
Slot |
Component |
Profile type |
|
Technical name |
Description |
||
1 |
CSEARCH_DISP |
CONTACT_SEARCH_CONFIGURATION |
|
2 and 4 |
ABOX_SLIM |
ACTION_BOX_CONFIGURATION_SLIM |
|
CALL_STATE |
Not required |
||
QUICK_KEYS |
QUICK_KEYS_CONFIGURATION |
||
5 |
NAV_AREA |
DEFAULT_WORKSPACES |
|
6 |
APPL_AREA_2 |
DEFAULT_WORKSPACES |
|
You can assign the
action box
and
function keys
to slot 2 and the call status to slot 4, or vice versa.
You can assign slots 5 and 6 to the
Navigation
and
Application Areas
. The
Navigation
and
Application Areas
can be used to include additional components.
See also: Navigation and Application Area
Slot 3 and slot 7 are not generally used. You can, however, assign the
solution database
(SOL_SEARCH) or a customer-specific component to these slots.
See also: Solution Search
See also: Customer-Specific Component
You can assign the visible components to a framework with a docking control as follows:
Slot |
Component |
Profile type |
|
Technical name |
Description |
||
1 |
CSEARCH_DISP |
CONTACT_SEARCH_CONFIGURATION |
|
2 |
ABOX_SLIM |
ACTION_BOX_CONFIGURATION_SLIM |
|
4 |
ISM_SCRIPT |
SCRIPT_PROFILE |
|
6 |
APPL_AREA_2 |
DEFAULT_WORKSPACES |
|
When the
Ad Spec Editor (ISMAM_EDITOR)
component is assigned to the invisible components, this framework provides a docking control that can be integrated with an editor for ad spec design.
See also: Ad Spec Editor
Assigning Invisible Components
Three types of hidden components are available:
Independent components
Components that are required for a visible component function
Components that can be used in a combination with a visible component
You can assign the following invisible components to a framework:
Type of component |
Component |
Description |
Profile type |
Independent components |
AUTOCALL |
Auto action |
AUTOCALL_PROFILE |
CALLBACK |
CALLBACK_ASSIGN_QUEUE_PROFILE |
||
CALLBACK_CONFIGURATION |
|||
CALLBACK_PROCESS_QUEUE_PROFILE |
|||
CIC_TOOLBAR |
TBAR_PROF |
||
CIC_TOOLBAR2 |
TBAR2_PROF |
||
HLOG |
Logging of Activities |
ACTIVITY_LOGGING_PROFILE |
|
ISMAM_EDITOR |
ISMAM_EDITOR_DOCKING |
||
Components that are required for a visible component function |
CTI |
Computer Telephony Integration for CALL_STATE |
CTIADM_PROF |
CTIQA_PROF |
|||
HIDDEN_ABOX |
Hidden Action Box for ACTION_BOX or ABOX_SLIM |
Not required |
|
HIDDEN SCRPT |
Hidden Script Display for SCRIPT_DISP |
||
ISM_HSCRIPT |
Hidden script display in
|
||
CSEARCH_HIDE |
Invisible business partner search for CSEARCH_DISP |
||
ISM_HSEARCH |
Invisible business partner search in
|
||
Components that can be used in a combination with a visible component |
BD_MARK |
Selection service with BD_DISPLAY |
BD_MARK_PROF |
CALLCTR |
Call Center with CALL_STATE |
CALL_CENTER_COMP_CONFIGURATION |
|
LAYOUTSWITCH |
Adjust size using application toolbar for NAV_AREA und APPL_AREA_2 |
Not required |