Feature Wiki

Information about planned and released features

Tabs

Mail

1 General

Maintainer and Tester

  • Mail
    • Authority to Sign off on Conceptual Changes: mjansen
    • Authority to Sign off on Code Changes: mjansen
    • Authority to Curate Test Cases: mjansen
    • Authority to (De-)Assign Authorities: mjansen (Databay AG)
    • Tester: Till Lennart Vogt/Test-Team OWL
    • Assignee for Security Reports: mjansen
    • Assignee for Security Issues: mjansen
    • Unit-specific Guidelines, Rules, and Regulations: LINK MISSING

 

Additional

Roadmap

Mid Term

Refactor Registration Process of Mail Template Context

Currently, mail template contexts can be defined in the component XML file. These files are processed by \ilMailTemplateContextDefinitionProcessor::beginTag and \ilMailTemplateContextDefinitionProcessor::endTag, which are called by the \ilComponentDefinitionReader.

Current Problems: * \ilMailTemplateContextService::getContextInstance is used in multiple contexts. * Certain dependencies (retrieved from $DIC) do not exist or are replaced with fake objects during setup, but the actual services are required in the constructors of the concrete implementations. * There should be an interface segregation for the registration of mail template contexts and the actual provided context which is responsible to provide/replace placeholders. * To solve the problem, the mail context implementations are currently created with the Reflection API in the setup context.

IRSS Integration

Files should be handled by the IRSS

 

2 Projects

The following projects are planned or have been realised for this component:

NEW Projects

Ongoing Projects

Projects On-Hold

Completed Projects

3 Suggested Features

In the following list you can add a request for a new feature or pick-up an already suggested feature about that should be decided again. The lists after show existing suggestions and scheduled features of this component.

  1. ...

SUGGESTED FOR 11

Already suggested

4 Scheduled Features

The following features have been scheduled / published in ILIAS Release 11:

The following features have been scheduled / published in ILIAS Release 10:

The following features have been scheduled / published in ILIAS Release 9:

The following features have been scheduled / published in ILIAS Release 8:

The following features have been scheduled / published in ILIAS Release 7:

The following features have been scheduled / published in ILIAS Release 6:

The following features have been scheduled / published in ILIAS Release 5.4:

The following features have been scheduled / published in ILIAS Release 5.3:

The following features are planned to be developed or already in development for ILIAS Release 5.2:

The following features have been scheduled / published in ILIAS Release 5.1:

The following features have already been developed and published in Release 5.0:

The following features have already been developed and published in Release 4.4:

 
The following features have already been developed and published in Release 4.3:
  • none
 
The following features have already been developed and published in Release 4.2: 
The following features have already been developed and published in Release 4.1: 
The following features have already been developed and published in Release 4.0:

5 Redundant and Rejected Feature Requests

Requests that are redundant (already implemented in other requests)

Rejected Feature Requests

Last edited: 22. Oct 2024, 13:43, Gruber, Ann-Christin [acgruber]