Please enable JavaScript.
Coggle requires JavaScript to display documents.
Risk userbased Licenses - Coggle Diagram
Risk userbased Licenses
New Version Polysun has bugs:
existing paid user cannot
register/signin
Update and sign-in request dos not work
Ability to send invite link to their own team
Password reset does not work
We need to be able to reset user's passwords
Admin User (network clients) don't sends invitation link
Track the users that need to invite their own users
user registration is not matched correctly to the existing UID Account
Contact users informing them of which account to use to access the new system: define email content & targets for the communication
Self migrate at login
user does not update the app
Define what to do with users who are not paying for SMA and are not getting updates.
Potentially contact users without SMA
application crashes or becomes otherwise unusable due to unforseen license situations
Test on platforms we support
Ensure way to revert back to Thales
License lock fails and the user cannot login despite having a technically valid license
New trial user has bad user experience
receives 2 emails or no emails
polyhub is not switched off
Email template plugin wocommerce is not switched off
Marketing automation hubspot for designer and standard is not setup.
The woocommerce store is still accesiblle
Signup trial process is buggy not working
Deeplinks of woo-commerce store (artikeldetailpage) are not redirected, before woo-commerce shop is switched off
Redirect all urls and indexes
User portal has bad translations or inconsistent naming/text
Translations as usual part of the dev process
Fallback available
Stripe is integrated in a way that causes issues and users can't go through the buy/trial process
Performance of the platform is acceptable when connecting from remote locations
Co-existence of thales activation and user based licesing causes errors
it department does not update the network version, network user, downloads software on desktop
webservice not working due to security/firewall of company
Provide technical information & guidelines to network clients to setup firewall correctly with targeted communication
Support proxy to connect to license server
Update license activation info window with port numbers and firewall setup info
What we recommend to IT department: to shut down the network version and let user update their desktop version or they need to maintain the network version?
Communicate migration process: leave network version on for now, communicate fallback plans, and workarounds
payment and invoicing process not automated
accounting process works only manually
Communication from team: what must be done for accounting and how the systems work
user migration
Some users cannot reached and will be without working license when Thales goes away
Licenses are missing from the migrated database and must be manually added
Communicate to users that they should contact us if anything is missing
Users are not matched to the migrated licenses and must ask for support
Forward compatibility to support future developments
workos can only be replaced in the future by breaking Polysun
dummy oath flow as fallback
security concerns