github-actions[bot]
commented
1 year ago Hi @christinaor, thank you for taking up this issue! Hfla appreciates you :)
Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)
You're awesome!
P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)
christinaor
Dependency
4555 once this possible solution is explored, we can see if this ER can be closed.
Emergent Requirement - Problem
Slack no longer allows API usage for non enterprise accounts. It works with a legacy token, but we lost ours. So no application that uses the API will work (slackin, etc.). However, there are other things we can do, so this ER describes the problem and potential solutions so that we can make some issues.
Issue you discovered this emergent requirement in
3433
Date discovered
2023-03-24
Did you have to do something temporarily
Who was involved
@ExperimentsInHonesty and many others
What happens if this is not addressed
Slack has made it so that you can create a link that never expires, but it expires after 400 invites anyway. So I keep generating a new link for every other onboarding (since I have no idea how many people have used it). Sometimes I forget and it doesn't work and I need to regenerate during the onboarding. This is going to become a major problem when we move to an automated onboarding via VRMS and someone has to reset the link manually every month.
Resources
Recommended Action Items
Potential solutions [draft]
I believe using a desktop based automation might be a way around this. UI path is the only one I know about, but they do have a community version and any skills people gained learning how to use it would be directly relevant to a job search (UI path Automation Engineers are in high demand).