Constraint / limitation | Mitigation |
|---|
No process can be created for Links / Actions | Keep clean naming of TVs and Links via the workflow ladder, but process can be created in the Spoke Model full of Links |
| |
ADO data can't be published to UX | Use a new/existing mapping model (e.g. GL merge, 9 screens) inner-joined with ADO data; don't map in the spoke |
Need to weigh requirements against limits | Per dataspace: 50 GB storage, 500 datasets, 1,000 model links execution limit per day, 500 data extracts per day. |
One module can be associated with only one link | Need to create a single TV from multiple data sources if required (ex. S4 and ECC attribute import into P6 Profit Center Attributes) |
Source to ADO to spoke data flow can only be through workflow | Train the CoE in Workflow. ADO to Spoke can be through CloudWorks |
No history/restore available | Access to ADO to be limited to avoid need to track history |
Error logs are vague | |
If a module name is changed, the ADO link breaks | Set up a subtask in Tech cleanup stories to check ADO links associated with modules renamed |
Workflow to ADO link not shown in ADO as ref by | Can use “Last Run” as a marker for if a Link has been used or ran |
Reformatting of Actuals/Bud. Adj./Capex Files | This may not even possible, and if it is, extensive testing will be required |
One environment; no opportunity for DEV/SBX/PROD | We could create different TVs that are Dev TVs/SBX TVs/PROD TVs, but that seems very risky since wrong data could potentially populate in the wrong place |
