|
Reuse the Context Information Template |
Scroll Previous Topic Top Next Topic More |
In this table of the script tab 1,2,3. Data Load (with ETL), you will rename the case-related fields. We distinguish the event log from the CaseInformation in order to create a clearly understandable data model. The CaseInformation table basically behaves like the EventLog table. There are CaseDimensionX fields that must be replaced.
|
Never delete "CaseID" because this is the connection between the CaseInformation and EventLog tables. |
1.Replace the CaseDimensionX fields (as in the Helpdesk example) with your case names.
2.If you don't have enough data for all fields, e.g. no data for CaseDimension5, replace the respective row with ProcessFinished, CaseStartDate, ProcessStartsWithActivityType, ProcessEndsWithActivityType as CaseDimension5.
If you need more fields than the template provides, simply insert them as new CaseDimension6 with the respective data field name.
For example, if you want to add a department, create a new row with a field named DepartmentName and name it as you like (e.g. "Department Name").
Left Join([CaseInformation_$(mvProcessDescription)])
LOAD distinct
CaseID, // don't delete it
CaseDimension1,
CaseDimension2,
CaseDimension3,
CaseDimension4,
CaseDimension5,
Geofield // for example: city
FROM [$(DataConnection)/mpmXData.qvd] (qvd);
Helpdesk example:
Left Join([CaseInformation_$(mvProcessDescription)])
LOAD distinct
PurchaseOrderItem as CaseID,
Supplier,
Company,
SpendArea,
ProductClass,
ProcessPathUniqueNo,
City
FROM [lib://helpdesk/HelpdeskEventlog.qvd] (qvd);
