[Video E-Learning]
Here you write the SQL that is used to get the Cards of the Kanban Boards (In above example Sales Opportunities). You can write the SQL you like as long as it up with a minimum of 3 Columns:
•PrimaryKey that contain the primary key of the object (use for updates and navigation). Example on an Invoice tht is the Field DocEntry •Caption that contains the title-caption of each card. This you should be something that identify the card (in ablve example we use the opportunity Id + name of the Opportunity) •ColumnValue that represent which of the Column on the Kanban Board the Card should be shown in. In above example we use the Current Stage the Opportunity is in. This value needs to be one of the values your Column SQL gives back (if it is not the Card will not be shown)
Beyond that there are a few optional columns you can also provide in order to get more information on the card or change the default colors (See video about these options)
•Description column Here you can write a summary description of the card that help the user better understand the card (In our Example which Business Partner the the Opportunity is for, the potential abount and the predited close date). You can use simplified HTML tags like Likebreaks (<br>) and Bold <b>someBoldText</b> to style your description: NB: Not all HTML tags are supported. See list here + [E-learning video on card formatting].
NB: Boyum Support will not help with HTML Formatting!
•ProgressPercentage column If you have an object that have a Percentage-based progress for you object you can pass this along in the SQL to show this visually on the card. o
•BackColor column can be used to control the background color of the cards. Example adding "'SkyBlue' AS BackColor," as a column will turn the cards blue (you can of cause use CASE statements to make different card different colors) o
•CaptionForeColor column works like the BackColor but controls the Colors of the Title Caption
•DescriptionForeColor column control the color of the center description similar to how CaptionForeColor control the title
•ProgressbarTextForeColor column controls the color of the Percentage text next to the progressbar
Tip: You can use the following color-names to set the color
•ObjectType column is an optional column you can provide to override the ObjectType on data level (If you example have both Sales Orders and Deliveries in same Kanban Board, in an advanced scenario). NB: The Overridden is an integer from one of the following:
Object Type Value
|
Object Description
|
97
|
Opportunity
|
17
|
Sales Order
|
234000021
|
Project
|
202
|
Production Order
|
22
|
Purchase Order
|
191
|
Service Call
|
23
|
Sales Quotation
|
15
|
Delivery
|
16
|
Return
|
13
|
AR Invoice
|
14
|
AR Credit Memo
|
234000031
|
Return Request
|
203
|
AR Down Payment
|
540000006
|
Purchase Quotation
|
20
|
Goods Receipt PO
|
21
|
Goods Return
|
18
|
AP Invoice
|
19
|
AP Credit Memo
|
1470000113
|
Goods Return Request
|
204
|
AP Down Payment
|
2
|
Business Partner
|
4
|
Item Master Data
|
171
|
Employee Master Data
|
9999991
|
Beas: Work Order
|
9999992
|
Beas: Item Master Data
|
9999993
|
Beas: Work Order BOM
|
9999994
|
Beas: Work Order POS
|
9999995
|
PMX WMS: Picklist
|
9999996
|
PMX WMS: Picklist Proposal
|
Optional @Keywords (aka can be used but not mandatory) [Warning: Keywords are case sensitive]
Keyword
|
Description
|
@UserId
|
This Keyword can be replaced with current logged in user's UserId (Field OUSR.INTERNAL_K in the database)
|
@UserName
|
This Keyword can be replaced with current logged in user's Username (Field OUSR.USER_CODE in the database)
|
@EmployeeId
|
This Keyword can be replaced with current logged in user's EmployeeId (Field OHEM.empID in the database for the Employee that is linked to current User)
|
@SalesEmployeeId
|
This Keyword can be replaced with current logged in user's SalesEmployeeId (Field OHEM.salesPrson in the database for the Employee that is linked to current User)
|
Tip: You can in Kanbans with source linked to Universal Functions, use the Dynamic Syntax to make a Kanban context sensitive
[E-learning on keywords]
|