This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Now that it's live, don't forget to accept your certification badge on Credly today! Learn more here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email email@example.com for assistance.
Hi, we have had a couple of customers that experienced some issues keeping Promote running properly. It would be nice if there was a central repository of information of potential failures that we can point out the the customers instead of having them dig for it in the community (or wait for support to do the digging). It would greatly help since a number of clients in my country are quite intimated with Linux.
One key challenge that we have is promoting regular canvasses (not just advanced analytics models).
It would be very useful if Promote could be made part of the core product of the server:
a) split the server into 1;2;3 environments (Dev; UAT; Prod)
b) Promote then manages the workflow to promote an asset between these environments, with a configurable workflow that allows for signoffs; diff checks; control checks (e.g. are people using tools in the right way; DB connection strings etc); and then writing a copy into the firm source-code repository.
c) Promote should also then change the links in canvasses to point to a prod version of the databases and APIs if relevant.
This process is currently extremely manual and labour intensive; so if we could apply the same Promote process to regular canvasses it would be a big time saving for our admin teams.