What is "Product id" and "Product key" in CA Workflow?

Document ID : KB000025896
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

This document explains the importance of "Product id" and "Product key" in a CA Workflow install.

Solution:

In R11, the MDB database is shared among different products. Several products employ CA Workflow and share the workflow tables. The following are the CA Workflow tables in MDB.

  • actors

  • assignments

  • definitions

  • workflow_groups

  • instances

  • objclasses

  • objstore

  • serviceproviders

  • setting

  • simpleevent

  • stats

  • timedevent

  • triggers

  • user_roles

  • users

  • wf_ids

  • worklist

  • wfschema

  • securitypredicate

  • workflow_configuration

  • ldapconfiguration

  • ldapactors_worklist

  • process_listeners

  • dynamic_worklist

  • workitems

  • instance_history

  • userlist_worklist

  • productids

  • wf_locks

All the above tables may contain data from different products. The data is partitioned between each product by means of a unique value called the product id. All CA Workflow tables have a "productid" column, the value in it denotes which application uses it.

The list of possible product ids in an environment is available in "productids" table. The important columns to look at in product ids table are

"productkey": It is a unique identifier code for a specific product. The product id for CA Service Desk is "USD:2003". This key is post fixed with an integer that gets incremented each time Workflow is installed.

"description": General description of the embedding product

"productid": the value that is used to mark data in other tables (in the "productid" column) as owned by the application specified in "productkey".

If CA Service Desk is currently only application running CA Workflow in the MDB, then only one row will be available in the "productids" table (see Figure 1):

Figure 1:

Figure1

The definitions table show the "productid" of the ServiceDesk install (see Figure 2):

Figure 2:

Figure 2