Update Custom Attributes for Governance Elements

Data entered in IGC™ and imported into dspConduct™ cannot be updated in dspConduct™. Records cannot be deleted, and elements cannot be activated or deactivated.

Additionally, a governance hierarchy imported from the IGC™ cannot have elements added or deleted (e.g., a Designer cannot add a scenario in dspConduct™ to a business process that was added in IGC™).

Some settings that are not set in IGC™ can be updated for IGC™ elements in dspConduct™.

NOTE: A Process Designer must assign an owner in dspConduct™ to any roles, scenarios, business processes or categories that were added in IGC™.

NOTE: By default, the initial business process scenario imported from IGC™ has a priority of 100. The priority of each subsequent business process scenario is incremented by 10. A user can update this value as needed.

NOTE: When a role is imported from IGC™ and the SLA fields are blank in dspConduct™, the values entered in IGC™ are used at the scenario role level and the business process scenario role level. If the fields already contain values in dspConduct™, the SLA values are not updated at these levels. At the role level, the SLA values are updated when a role is imported from IGC™ with SLA data whether the fields have values in dspConduct™ or not.

Governance elements added in IGC™ are not used in dspConduct™ to create new business processes. For example, a role added in IGC™ cannot be used in a scenario added in dspConduct™.

NOTE:All IGC™ elements can be copied as the basis for a new element that can be used in dspConduct™.

The following settings and features are available to update for IGC™ elements in dspConduct™.