Professional Documents
Culture Documents
No Question
1 Foreign Key
3 Natural Keys
Foreign Keys define a relationship between multiple Data Tables ensuring data integrity and
consistency, and reducing the cost of data management and complexity when querying,
usyally,Administrators can define a maximum of five Foreign Keys per child data table, as
there is a limitation of five indexed columns per data table.
Live Data Tables immediately reflect saved changes to table queries without a deploy.
The saved changes are immediately available for queries from SOAP APIs, REST APIs, BML
functions, Export, Bulk Download, and Migration.
Natural Key can be a single column or a combination of several columns that produce a
unique identifier for each record (row)
Natural Keys are supported in: Data Tables, Web Services API, CSV Upload and Bulk Upload.
Secure Data Table Columns provide a method for securely storing confidential credentials in
CPQ
Secure columns always store the encrypted form of the data in the data table. The only way
to access this data in its original, decrypted form is through BMQL.
result ="";
records= bmql("select Secured from dummyTable");
for record in records{
result= get(record,"Secured");
print result;}
return "";
The primary key is a unique value that identifies each record. ... A natural key is a single
column or set of columns that uniquely identifies a single record in a table,
Relevant Code/Info
S.No Question
1 What are the different file formats in which you can export a proposal?
Designer
The Document Designer editor’s intuitive user interface and drag and drop functionality makes
document design and maintenance fluid and efficient.
Engine
The Document Engine powers the Oracle CPQ Proposal Generator and the Oracle CPQ Contract
Generator.which will work on XSL coding.
Project
1 Add Submit Button
2 Add Discount Level Approval
3 Add Total Level Approval
4 Add Any Speacial Approval
5 Add Dyanamic approver
6 Add static Approver
7 Trigger all the approvals on the UI
1-Transition rules we will create for move from one step to an other step when an action is clicked
2-Within transition rules we can also set up email, fax, or XML notification to trigger when an action occurs.
We can send the notifications from the define notications under the transition rule,Timers and dynimically
we can send through approvals
There are 4 sub set actions under the submit action
(request /reject/approve/Revise)
There are two approval flows
1)Serial
2)Parallel
Parallel-In a Parallel Approver Sequence, both approvers have to approve the quote for it to be considered
"approved" and move to the next Step in the workflow.
This will be done majorly at same level of people EX-Sales Rep
Serial-In a Serial Approver Sequence, the quote must be approved by a first-level approver before moving on
to the next approver.
This will be done at different level of people EX- Sales Rep,Manager,Director
1-Constraint Rule
2-Validation Rule
3-Hiding Rule
4-Filter Rule
json
jsonput
jsonget
jsonremove()-->returns true if it removes key and object
jsonkeys()
isjsonnull()-
jsonpathgetmultiple-->Returns the value(s)/path(s) from a JSON object
corresponding to a given JSON pa
str = "{\"key1\":90,\"key2\":[{\"key1\":900}],\"key3\":{\"key1\":9000}}";
arrayVals = jsonpathgetmultiple(jsonObj,"$..key1");
//Output: [90,900,9000]
Bmql ( select attr from transaction or trnsactionline)
Commerce rules will run (Hiding, then constraints, then validations).
Util BML Library - The functions in this library can be accessed and called
throughout CPQ.
We can call only system attributes
Commerce Library-The functions in this library can be accessed only in specific
Commerce Process and called throughout CPQ.
We can call only main ,sub document and system attributes as well
Remove
[sub-
document]
Open [sub-
document]
Create [next
main
document]
Reconfigure
*
Recalculate
*
Create [sub-
document] *
Autofill/
Browse/
View/Select
Alternate
Address
Why the configuration Flow Rule is used and what are the different Nodes are
4 used in the system
Configuration Flows help arrange and organize configuration attributes to make Configuration user-
friendly.
Start Node: Where the Configuration Flow will begin. You can have more than one start node, so if
you plan on having multiple, this will be what you set your beginning nodes to.
End Node: Final node of the flow. This is where you'll see your action buttons like Add to Quote, as
well as any recommended line items. As with start nodes, you can have multiple end nodes. The
proper end node is set by attributes in the condition.
Start and End Node: Start and End Nodes are combined.
Transition Node: Transitions user from one node to another based on attribute selections.
Primary Start Node: When there is more than one start flow, this lets the application know to start
here first.
Primary Start and End Node: Primary Start and End nodes are combined.