Skip to Main Content
Idea Portal
Status In Review
Categories Functionality
Created by Benjamin Schaller
Created on Feb 15, 2024

Make Subscription-Events configurable per DocumentClass

We are using Instance-Subsciptions a lot, but in standard they are barely usable. When creating a new Instance-Subscription all events are ticked by default, but rarely all of them are needed (most of the time we only need 1-2). Also the names of the events are very technical and most of our users would not understand anyway, so we just want to configure defaults per document-class.


Currently we need to update every created subscription with an agent, to make sure the right events are selected. In the future we would like to configure these events in cubeDesigner.

  • Attach files
  • Benjamin Schaller
    Reply
    |
    Apr 17, 2024

    Hi Douglas,

    We definitely need a way to define defaults so that our users do not have to select the correct events themselves. They do not understand Doxis in a way that would allow them to distinguish what is relevant within the application they are subscribing to.

    We give them the ability to 'subscribe' with one click and receive notifications for the relevant events that we have predefined for this process. The events that are relevant are individual per use case, which in our case is mostly per document class.

    I can give you some examples, but as I said, they are very individual, depending on the type of application. One example would be our globally managed corporate documents, where we have set up a subscription for "Logically delete document" and "Create new published version". This way, users are notified when a document they are subscribed to is deleted or when a new version is created. Some of the other events are also triggered regularly in this process (e.g. create document versions, replace content, check in, check out), but we do not want users to be informed about them.

    Best regards,

    Benjamin

  • Admin
    Douglas Cardoso
    Reply
    |
    Apr 16, 2024

    Hi Benjamin,

    I understood the problem and agreed with you. What I'm not sure, though, is whether the default configuration per class is the right way. What are the most common events you would like to be informed about?

    We could, for example, group different fine-granular events into one called content modification, permission change, etc.

    It would be helpful if the other users who voted for this feature also share their feedback.

    Thanks,

    Douglas