Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-plugins fusiondirectory-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #5906
Closed
Open
Issue created Jan 16, 2019 by bmortier@bmortierMaintainer

Support Supann 2018

Hello,

SupAnn as been revised and there is https://services.renater.fr/documentation/supann/supann2018/recommandations2018/index

This ticket is mean to be a global ticket as support for SupAnn 2018 will be gradually added following customer demand and community contributions

Cheers

linked ticket

  • SupAnn 2018 account life cycle #5907 (closed)
  • La carte multi-services #6015 (closed)
  • SupAnn 2018 second revision new schema, lists and fields #6024 (closed)
  • add supannParrainDN attribute in the supann plugin #6043 (closed)
  • FranceConnect and civil status #6111 (closed)
  • Add support for supannConsentement #6025 (closed)

Revision 2

SupAnn 2018 had a second revision: https://services.renater.fr/documentation/supann/supann2018/recommandations2018/fonctionnel/revisions2018

  • supannConsentement: This is a complicated one, most likely we’ll have to support this as a free field since there is a lot of possible values and tags. It is also hard to exploit when showing data.
  • supannAdressePostalePrivee, supannTelephonePrive, supannMailPrive may be added to SupAnn tab. Sounds like supannMailPrive is redundant with supannnMailPerso but it is not said that supannMailPerso is deprecated.
  • homePostalAddress, homePhone seem to be used to indicate which value of supannAdressePostalePrivee and supannTelephonePrive is the main one as I see it, so we may implement them like this.
  • The schema changes from last revision are only added attributes so update is safe.
  • We also need to update nomenclatures to make sure they reflect the last data.
Edited Jul 29, 2021 by bmortier
Assignee
Assign to
Time tracking