🆔FP: SharePoint integration
This feature passport contains all information necessary [available up to date] to build an integration with a SharePointlist.
Status Feature Passport
| STATUS | OWNER | DATE |
|---|---|---|
In proposal (WIP) | Sofie | 20/01/2022 |
In refinement - Design Research | ||
In refinement - Technical Research/Feedback | ||
In development | ||
In QA/ Testing | ||
In Final state |
JIRA
Epic = OP-940: SharePoint integration
Analysis
Current state
There is no connection to SharePoint (SP) at the moment.
In case of worship services, the three converted SharePoint lists are no longer used by any department after conversion. At the moment they are still read-only available in SP though, but they are not up to date anymore and probably will be deleted in the future.
In case of other data, like the data from the two SharePoint lists (organizations and contacts) of Local Finance, they should be converted to the OP, but the SharePoint lists will continue to be used (read only) by the users.
Why do we need a SharePoint integration?
After data conversion of some lists, some SP lists will (temporary) continue to exist because:
we will not convert all columns in the SP list
we will not convert all records immediately (conversion per administrative unit, because they all have different requirements)
some other SP lists are dependent on the converted SP list, as a whole or on specific columns. In the future, it is possible that the SP list is no longer needed, but we can not guarantee that.
the business still wants to use the functionalities of SharePoint to export, group and filter data
Overview of contactlists in SharePoint
Other contact lists in SharePoint: OP_SP_Overzicht_ABBContactlijsten.xlsx (list is updated by Sarah MacQuoy of the SharePoint team)
We start with converting the SP organisation list of LF (Lokale Financiën) because that SP list is considered to be the mother list of contacts used within ABB.
Expectations
In this feature passport, we will tackle these future expectations:
[the analyst expresses the expectations that need to be met in order to finish this feature]
The analyst does not provide with solutions. This is the task of the technical and design team.
e.g.
❌ There should be a button in the bottom-left corner so the user can send an email
✅ The user needs the ability to send emails to customer service
After the analyst is done with this, there needs to be a meeting (this can become part of the BRM) where the analyst talks through the expectations with the technical and design team. The team can then decide which expectations are feasible for this feature and create tickets accordingly.
This means that if, for example, the technical team thinks that one of the expectations for this feature will take a lot longer than the analyst anticipated, the PO can still decide the work on that expectations as part of another feature passport (* this then needs to be amended in the expectations and a new feature passport can be created.)
Once the team has agreed on the expectations and the tickets have been created, acceptance criteria can be added on the tickets in jira.
This includes any dependencies, e.g.: Story: A user needs to be able to add a position to person Acceptance criteria:
The position needs to be automatically added to the relevant organisation
The position needs to be automatically added to the list of all the positions
Technical analysis
OP-859: Technical analysis: Synchronisation OP data to SharePoint lists
How can we synchronize the data from OP with the SharePoint lists that continue to exist (read-only)?
The SharePoint lists themselves no longer need to be edited, the data will be updated in the OP.
OP-860: Technical analysis: Convert SharePointlist partially
Is it possible to convert SharePointlist partially to the OP, or is is that not a good idea?
If it's possible, first import data that fit in the module ‘bestuurseenheden’ and ‘persons’.
If it's not possible, we need to develop the module 'Ondernemingen & Verenigingen’.
Questions for development
Questions for Serge of the ABB architecture team
Available data for POC
A copie of the two 'Lokale Financiën' LF SharePoint lists, which can be used for test purposes, are available on OP SharePoint:
❗The list gets updated automatically via a script. Please take that into account if you encounter unexpected results during testing. [The script was written by Nicholas Van Gaster (tobeyn), contact Sarah Macquoy]
Solution
The next two parts of the FP can [sometimes] be worked on simultaneously
Design
User research
Not needed in this FP > to be confirmed.
Mock-ups
Not needed in this FP > to be confirmed.
Technical
This part of the feature passport is owned by the technical team
[Information about the technical solutions for expectations that need it - e.g. using mu-search for showing all types of positions in one table.]
After the designer and/or the technical team finish their task, a meeting follows where the solutions are presented. The team exchanges feedback and amends the feature passport where necessary.
Last updated