Explore topic-wise InterviewSolutions in .

There are three elements i.e Users ( Who want ACCESS ) , ACTIONS ( What kind of Access ) and Resources ( WHOSE Access ). The RELATIONSHIP between resource and user is store in ACRELATION table and ACRESREL associate a resource and relationship.

There are three elements i.e Users ( Who want access ) , Actions ( What kind of Access ) and Resources ( Whose Access ). The relationship between resource and user is store in ACRELATION table and ACRESREL associate a resource and relationship.

STEP 1 - Create a new policy definition by adding record in tables POLICY, POLICYDESC.

Step 2 - ASSOCIATE the new policy with its terms and conditions by adding a record in relationship table POLICYTC.

Step 3 - Associate commands to the new policy by adding records in POLICYCMD.

Step 4 - ADD REFERENCE to the policy in the repective contract xml file.

Step 1 - Create a new policy definition by adding record in tables POLICY, POLICYDESC.

Step 2 - Associate the new policy with its terms and conditions by adding a record in relationship table POLICYTC.

Step 3 - Associate commands to the new policy by adding records in POLICYCMD.

Step 4 - Add reference to the policy in the repective contract xml file.

wc-server.xml STORES the DB configuration. We can EITHER change it MANUALLY or by using setdbtype command.

wc-server.xml stores the DB configuration. We can either change it manually or by using setdbtype command.

REMOVE the JSP ENTRY from cachespec.xml.

Remove the jsp entry from cachespec.xml.

By QUERYING the STATUS from the ORDERS table.

By querying the STATUS from the ORDERS table.

a. CREATE NECESSARY lzx files( template , OBJECT definition and properties ), make config entries and then Build OPEN Laszlo project ( for LOBTools ) so that new promotion type should be displayed in MANAGEMENT center.
b. Create a new promotion type xsl ( promotion type template ) and then map it to the promotionn type.

a. Create necessary lzx files( template , object definition and properties ), make config entries and then Build open Laszlo project ( for LOBTools ) so that new promotion type should be displayed in management center.
b. Create a new promotion type xsl ( promotion type template ) and then map it to the promotionn type.

PURCHASE CONDITION is the condition that must be fulfilled before a promotion is applied and Reward is the benefit that is passed to customer.

For Example: If promotion is "Buy 2 QUANTITY of X, Get Y Free" , Purchase condition is INCLUSION of 2 qty of X in CART. Reward in this case would be 1 qty of Y.

Purchase condition is the condition that must be fulfilled before a promotion is applied and Reward is the benefit that is passed to customer.

For Example: If promotion is "Buy 2 Quantity of X, Get Y Free" , Purchase condition is inclusion of 2 qty of X in Cart. Reward in this case would be 1 qty of Y.

Promotions are created either using Management Center or ACCELERATOR. PX_PROMOTION table is used to STORE Promotions. COMPLETE PROMOTION is stored as an XML STRING within XMLPARAM column.
Other tables which are used to store promotion related information are:

CATENTCALCD

CALCODE

CLCDPROMO

Promotions are created either using Management Center or Accelerator. PX_PROMOTION table is used to store Promotions. Complete Promotion is stored as an XML string within XMLPARAM column.
Other tables which are used to store promotion related information are:

CATENTCALCD

CALCODE

CLCDPROMO

Item is a sale-able merchandise where as Product is a group of sale-able merchandise which share certain attributes. For example - Cell PHONE is a product whereas Samsung GALAXY S2 - White is an item.

Quantity is always attached to SKU ( Stock keeping unit ) or items. Product quanity has no relevance in TERMS of identify the current stock or reorder CONDITION. 

Item is a sale-able merchandise where as Product is a group of sale-able merchandise which share certain attributes. For example - Cell phone is a product whereas Samsung Galaxy S2 - White is an item.

Quantity is always attached to SKU ( Stock keeping unit ) or items. Product quanity has no relevance in terms of identify the current stock or reorder condition. 

Controller COMMAND is the command that gets called upon a request, just like We have actions in struts and controller in Spring. Task is a step in this bigger process. Task command are the commands that perform SPECIFIC task for a controller command, like service classes in other frameworks. In order to complete the request, a controller command may INVOKE multiple task commands.

Other difference are:

1. There is a URL mapping for controller command whereas Task command don't have URL mapped to them.
2. Controller command gets invoked before the task command.

Controller Command is the command that gets called upon a request, just like We have actions in struts and controller in Spring. Task is a step in this bigger process. Task command are the commands that perform specific task for a controller command, like service classes in other frameworks. In order to complete the request, a controller command may invoke multiple task commands.

Other difference are: