Under Community Review

Thanks for the post! Could you walk through the use case a bit more? Typically, objects will be in the baseline as a result of actions by users who do have permissions to edit the relevant "referencing" objects – broadly speaking topics and maps being those that most refer to other objects. So it would be good to hear about the specific use case – how the outcome that you'd be looking to achieve fits in your general flow and involved users for publications.

(Also this may help spark ideas from other Community members who have solved similar problems in different ways.)

Thanks again,

Joe

Allow customizations on freeze baseline action

Existing plugin mechanisms doesn't allow to intervene the freeze baseline action. Need customization capabilities, in order to execute business rules on freeze baseline action. Business rules like restricting the usage of objects in baseline, even though user has read access on them.

Parents
  • In our case, we are integrated with configuration management systems to receive the metadata for authoring a publication. The received metadata is stored in a fixed topic and map metadata fields.

    1. Always selecting latest version of the fixed topic/map.
    2. Restricting reuse of uncontrolled topics.

    Above use cases can only be possible if we can intervene the baseline freeze action. Hope I have given meaningful use cases to think on possible solutions/update to the product. Thank you for your comment Joe.

Comment
  • In our case, we are integrated with configuration management systems to receive the metadata for authoring a publication. The received metadata is stored in a fixed topic and map metadata fields.

    1. Always selecting latest version of the fixed topic/map.
    2. Restricting reuse of uncontrolled topics.

    Above use cases can only be possible if we can intervene the baseline freeze action. Hope I have given meaningful use cases to think on possible solutions/update to the product. Thank you for your comment Joe.

Children
No Data