CA Service Management

We have been asked to build "tools" to load Change Categories as this is a major drain on our Change Management organization resources.

We have built "tools" to create files for loading the categories, their properties and workflow.

However, when the workflow is inserted, the Behaviors for each do not come across.  It is not clear how best to load/relate them.  This is where the help is needed.

My thesis - it appears (please correct me) that new rows need to be inserted into the Behavior_Template (bhvtpl):

1. What object/table is the source of that data -- [usp_]lrel_status_codes_tsktypes??
2. If the Behavior_Template is the correct object, what data goes into the context_attrval column?

Thanks.

Hi Sam.

When creating new task templates (wftpl) in a change category (chgcat) through the GUI, the system is doing a lot for you in the background. I allways call it the "business logic", which is mostly defined in the "object layer" of the application. The problem is, when loading data with the pdm_load tools, this business logic is not triggered, and you have to somehow rebuild this logic, allways hoping, that "your" logic does the same as the business logic.

So, what's next:

• You could try to port your scripts to those who are using the business logic, for example writing so called fragment files interpreted by bop_cmd, or, fully  supported, using webservices. This would be my prefrerred recommendation.
• Figuring out all the details, and, as said before, hoping all runs well.

To answere your questions:

1. You are right. Each task (wf) and task template (wftpl) belongs to a task type. A task type represents more or less a list of valid status. This list of "valid" status for a task type is stored in the lrel_status_codes_tsktypes factory. When creating a new task template for a change category and setting the task type for this new task template, the system iterates through all "valid" status of this task type, and adds a behaviour template (bhvtpl) for the task template for each "valid" status. (business logic)
2. The context_attrval seems to be the id value of the corresponding task status (tskstat).

Hope that helps a bit, and kind regards

.............Michael

So I tried to pdm_deref the task field in Workflow_Task_Template via the tskty field to get the taskstat value in usp_lrel_status_codes_tsktypes. It returns only the first match.  I need to get all of them.

Suggestions?

Sam Cohen, Global Systems Manager

Marsh & McLennan Companies

Global Technology Infrastructure (MGTI) | ESE Application Engineering

121 River Street, Hoboken, NJ 07030, USA

+1 201 284 5213 | Mobile +1 908 472 0027 | sam.cohen@mercer.com<mailto:sam.cohen@mercer.com>

www.mmc.com<http://www.mmc.com/>

Hi Sam.

This cannot be done by a simple pdm_deref but should be processed in a script. In short:

1. pdm_load the task with the correct task type
2. iterate through each valid task status for this task type (lrel_status_codes_tsktypes), and load an appropriate bhvtpl record.

Regards

............Michael

With some assistance from this thread (thank you all), we have built a series of Excel workbooks to create loads for:

• Categories
• Category Properties
• Category Workflows AND related Status type (aka Behaviors)
• Behavior on True AND Behavior on Falise

There were some "shortcuts" taken for making data references, based on the relatively static nature of some of the data (like Task types).  If we add a new Task type we will need to update the workbook.

The audience is also very limited, so management is relatively easy.

CA SDM Loading Change category