In this use case there are a 3 dynamic lists on a service item that need to display different options for different departments. The data is currently set up in three data sets, one for each question. The supporting team is adjusting how they support this data and want an additional view into the entire service item, primarily for exporting/reporting purposes and moving between environments.
- Know what the data is, how it is currently used, and how it will be used
- Know how the data is currently managed/edited, and decide how you will want to manage/edit the data
- Decide how to categorize and retrieve the data
- Create the Data Set
Know What The Data Is, How It Is Currently Used, And How It Will Be Used
When creating a new dataset using existing data, it's critical to know what that data is and how it is currently used. The data points are:
- Service Item
- Question Name
- Answer Label
- Answer Value
This data is, in this example, be used to display different answers in these questions for each department. In 2 of the questions, there are some values that are displayed for all departments.
Valid values for the data are as follows:
- Catalog: My Catalog
- Service Item: Hardware and Software Update
- Question Name: Item Set, Software Name, Delivery Set
- Department: HR, Administration, IT, Project Management, Printing, All
- Answer Label: varies
- Answer Value: varies
For this case, a data set will be created that views all three questions in one data set, primarily for exporting/reporting purposes and moving between environments.
Decide How You Will Want To Manage/Edit The Data
The valid values for Answer Label and Answer Value might be any data, but for the other information, they should only select from the specific values listed.
This data should be managed by the people who "own" the Hardware and Software service item, Calbro Services->IT Support->Backoffice Support. To use this group, the group number is needed; this is group number 1000000003. The correlation between Support Groups and group numbers is available in this form: CTM:SYS-Access Permission Grps.
This data, in this use case, would be managed by question. There isn't any reason the data managers, for the sake of this particular example, would want to export or import all of this data together. It is more likely that they will want to import/add/remove/update values per question.
Decide How to Categorize and Retrieve This Data
This data is stored, for this example, in KS_SRV_Helper. There are 3 data sets set up:
|Index 1||Index 2||Index 3|| |
Data Set Name
|My Catalog||Hardware and Software Update||Item Set||HW and SW Item Set|
|My Catalog||Hardware and Software Update||Delivery Set||HW and SW Delivery Set|
|My Catalog||Hardware and Software Update||Software Name||HW and SW Software Name|
Now, the new dataset can look like this:
|Index 1||Index 2||Index 3|| |
Data Set Name
|My Catalog||Hardware and Software Update||HW and SW Dynamic Menus|
The categorization for viewing on the console can be the same as before:
- Dynamic Menus
- My Catalog
- Hardware and Software Update
Then the data set name will come up under that.
The data is stored:
- Catalog: Index Field 1
- Service Item: Index Field 2
- Question Name: Index Field 3
- Department: Character Field 1
- Answer Label: Character Field 2
- Answer Value: Character Field 3
Create The Data Set
Click the "Add New Data Set" on your DMC (http://<webserver><:port>/kinetic/DisplayPage?name=datamanagement).
Add the Data Set Name, Managing Group, and Categorization as determined in the previous set up steps are the same as the previous data sets except for the Bridge Qualification. In this case, just Index 1 and 2 are used to find the data. If this dataset was supposed to just allow a view into the data and exporting of the data. The setup listed here would be identical except for the "Service Item for editing data" question. That can be set to None if the data set is for viewing only, even if the data is in a form for which editing is possible.
Next add the bridge parameters, one at a time, to the table of Bridge Parameters. This is how the DMC will find the data for this data set. This is also the same as before, only with just Index 1 and 2.
The next steps are to configure the field that should be used as a unique ID and as the status value. The Unique ID and Status details default to acceptable values for this case.
So all that's left is defining each data point:
For the first two data points, we won't need to display them in the table because they are supporting data that helps define the data set. We want to lock them for editing (on row add or update) and set the correct value in as the default.
This time, for the third column, there will be the choice of the three question names and this should be visible in the table.
For the next data points, they will look exactly the same as they did in the previous data sets.
Then all of the data is in place for this data set:
Click "Add Row" to submit this data set.
Now the new data set will be available in the DMC. It will display the data from all three questions, from all three other datasets. In addition, it will allow for import and export of data that is also in the separate, smaller data sets.