- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 03:22 AM
Hi everyone!
I'm testing this new property (csdm.lifecycle.sync.between.ci.and.asset.activated) in a fresh Yokohama PDI and I observed that it is part of the condition in the "Update life cycle from legacy" Business Rule.
When this property is set to "true", CI and Asset life cycle are directly synced. However, when CIs without Assets are created, Life Cycle Stage/Status is empty by default. Based on the documentation, the legacy fields for CIs will sync through the asset and the asset will sync back to the CI.
What if CIs are virtual and do not have physical assets, will this system property not be appropriate for that use case? Is it recommended to have this system property and create customizations on assigning Life Cycle Stage/Status for CIs with no asset?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2025 10:48 PM
Key Observations
Synchronization Behavior: When the csdm.lifecycle.sync.between.ci.and.asset.activated property is set to true, it facilitates the synchronization of life cycle stages and statuses between Configuration Items (CIs) and their associated assets. This synchronization is managed by the "Update life cycle from legacy" business rule.
CIs Without Assets: In scenarios where CIs do not have corresponding assets—such as virtual machines or cloud resources—the life cycle stage and status fields may remain unpopulated. This is because the synchronization relies on the presence of an associated asset to propagate life cycle information.
Implications for Virtual/Cloud CIs: For CIs representing virtual or cloud resources without physical assets, relying solely on this system property may lead to incomplete life cycle data. This can affect reporting accuracy and downstream processes that depend on life cycle information.
Recommendations:
Custom Business Rules: Implement custom business rules to assign default life cycle stages and statuses to CIs that do not have associated assets. This ensures that all CIs have consistent and complete life cycle information.
CI Class-Based Logic: Utilize CI class-based logic to define default life cycle values for specific CI types, such as virtual servers or cloud resources. This approach allows for more granular control over life cycle assignments based on CI classifications.
Documentation and Standardization: Establish internal documentation and standards that outline how life cycle information should be managed for CIs without assets. This promotes consistency and clarity across the organization.
Evaluate Property Activation: If a significant portion of your CIs lack associated assets, consider whether activating the csdm.lifecycle.sync.between.ci.and.asset.activated property aligns with your organization's data management strategy. In some cases, it may be more appropriate to manage life cycle information through custom mechanisms rather than relying on this property.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2025 10:02 PM
Please see the link below for detailed information about the plugin.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2025 10:48 PM
Key Observations
Synchronization Behavior: When the csdm.lifecycle.sync.between.ci.and.asset.activated property is set to true, it facilitates the synchronization of life cycle stages and statuses between Configuration Items (CIs) and their associated assets. This synchronization is managed by the "Update life cycle from legacy" business rule.
CIs Without Assets: In scenarios where CIs do not have corresponding assets—such as virtual machines or cloud resources—the life cycle stage and status fields may remain unpopulated. This is because the synchronization relies on the presence of an associated asset to propagate life cycle information.
Implications for Virtual/Cloud CIs: For CIs representing virtual or cloud resources without physical assets, relying solely on this system property may lead to incomplete life cycle data. This can affect reporting accuracy and downstream processes that depend on life cycle information.
Recommendations:
Custom Business Rules: Implement custom business rules to assign default life cycle stages and statuses to CIs that do not have associated assets. This ensures that all CIs have consistent and complete life cycle information.
CI Class-Based Logic: Utilize CI class-based logic to define default life cycle values for specific CI types, such as virtual servers or cloud resources. This approach allows for more granular control over life cycle assignments based on CI classifications.
Documentation and Standardization: Establish internal documentation and standards that outline how life cycle information should be managed for CIs without assets. This promotes consistency and clarity across the organization.
Evaluate Property Activation: If a significant portion of your CIs lack associated assets, consider whether activating the csdm.lifecycle.sync.between.ci.and.asset.activated property aligns with your organization's data management strategy. In some cases, it may be more appropriate to manage life cycle information through custom mechanisms rather than relying on this property.
