Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
This is not a new idea, because the main functionallity already exists.
BUT, There is one part missing. The extension manager that triggers the events.
According to the documentstion:
<!ELEMENT task (run)*>
class CDATA #REQUIRED
id IDREF #REQUIRED
description CDATA #IMPLIED
runOnStart (true | false)
triggered (true | false)
filter CDATA #IMPLIED>
•class - Fully qualified class name, must extend com.ibm.dots.task.AbstractServerTask. •id - Unique id for this task •description - Task description •runOnStart - Indicates if the task should be run once when the javaddin task starts. True by default •triggered - If true, this task will be triggered by extension manager event. RunWhen contains the information about the event. •filter - Optional class that must implement the com.ibm.dots.task.ITaskFilterITaskFilter interface to dynamically prevent this task from loading in the container.